- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for accept (0.14 sec)
-
docs/throttle/README.md
Example: Limit a MinIO cluster to accept at max 1600 simultaneous S3 API requests across all nodes of the cluster. ```sh export MINIO_API_REQUESTS_MAX=1600 export MINIO_ROOT_USER=your-access-key export MINIO_ROOT_PASSWORD=your-secret-key minio server http://server{1...8}/mnt/hdd{1...16} ``` or ```sh
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.4K bytes - Viewed (0) -
docs/metrics/healthcheck/README.md
### Cluster-writeable probe The reply is '200 OK' if cluster has write quorum if not it returns '503 Service Unavailable'. ``` curl http://minio1:9001/minio/health/cluster HTTP/1.1 503 Service Unavailable Accept-Ranges: bytes Content-Length: 0 Server: MinIO Vary: Origin X-Amz-Bucket-Region: us-east-1 X-Minio-Write-Quorum: 3 X-Amz-Request-Id: 16239D6AB80EBECF X-Xss-Protection: 1; mode=block
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jul 06 16:18:38 GMT 2023 - 2.5K bytes - Viewed (0) -
docs/docker/README.md
``` ### MinIO Custom Access and Secret Keys using Docker secrets To override MinIO's auto-generated keys, you may pass secret and access keys explicitly by creating access and secret keys as [Docker secrets](https://docs.docker.com/engine/swarm/secrets/). MinIO server also allows regular strings as access and secret keys. ``` echo "AKIAIOSFODNN7EXAMPLE" | docker secret create access_key -
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 8.2K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
# How to secure access to MinIO on Kubernetes with TLS [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io) This document explains how to configure MinIO server with TLS certificates on Kubernetes. ## 1. Prerequisites - Familiarity with [MinIO deployment process on Kubernetes](https://min.io/docs/minio/kubernetes/upstream/operations/installation.html). - Kubernetes cluster with `kubectl` configured.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
### 2. Configure authentication type for Prometheus metrics MinIO supports two authentication modes for Prometheus either `jwt` or `public`, by default MinIO runs in `jwt` mode. To allow public access without authentication for prometheus metrics set environment as follows. ``` export MINIO_PROMETHEUS_AUTH_TYPE="public" minio server ~/test ``` ### 3. Configuring Prometheus
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/kms/README.md
export MINIO_ROOT_PASSWORD=minio123 minio server ~/export ``` > The KES instance at `https://play.min.io:7373` is meant to experiment and provides a way to get started quickly. > Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES > instance in production. ## Configuration Guides A typical MinIO deployment that uses a KMS for SSE-S3 looks like this: ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/ftp/README.md
## Scope - All IAM Credentials are allowed access excluding rotating credentials, rotating credentials are not allowed to login via FTP/SFTP ports, you must use S3 API port for if you are using rotating credentials. - Access to bucket(s) and object(s) are governed via IAM policies associated with the incoming login credentials. - Allows authentication and access for all
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 30 15:15:45 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/multi-tenancy/README.md
```sh export MINIO_ROOT_USER=<TENANT1_ACCESS_KEY> export MINIO_ROOT_PASSWORD=<TENANT1_SECRET_KEY> minio server --address :9001 http://192.168.10.1{1...4}/data/tenant1 export MINIO_ROOT_USER=<TENANT2_ACCESS_KEY> export MINIO_ROOT_PASSWORD=<TENANT2_SECRET_KEY> minio server --address :9002 http://192.168.10.1{1...4}/data/tenant2 export MINIO_ROOT_USER=<TENANT3_ACCESS_KEY> export MINIO_ROOT_PASSWORD=<TENANT3_SECRET_KEY>
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
docs/site-replication/README.md
- Creation and deletion of buckets and objects - Creation and deletion of all IAM users, groups, policies and their mappings to users or groups - Creation of STS credentials - Creation and deletion of service accounts (except those owned by the root user) - Changes to Bucket features such as: - Bucket Policies - Bucket Tags - Bucket Object-Lock configurations (including retention and legal hold configuration)
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0) -
docs/multi-user/admin/README.md
## Get started In this document we will explain in detail on how to configure admin users. ### 1. Prerequisites
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 4.5K bytes - Viewed (0)