2.3 KiB
2.3 KiB
MinIO Server Limits Per Tenant
Erasure Code (Multiple Drives / Servers)
| Item | Specification |
|---|---|
| Maximum number of servers per cluster | no-limit |
| Maximum number of federated clusters | no-limit |
| Minimum number of servers | 02 |
| Maximum number of drives per server | no-limit |
| Read quorum | N/2 |
| Write quorum | N/2+1 |
Browser Access
| Item | Specification |
|---|---|
| Web browser upload size limit | 5 TiB |
Limits of S3 API
| Item | Specification |
|---|---|
| Maximum number of buckets | no-limit |
| Maximum number of objects per bucket | no-limit |
| Maximum object size | 5 TiB |
| Minimum object size | 0 B |
| Maximum object size per PUT operation | 5 TiB |
| Maximum number of parts per upload | 10,000 |
| Part size | 5 MiB to 5 GiB. Last part can be 0 B to 5 GiB |
| Maximum number of parts returned per list parts request | 10000 |
| Maximum number of objects returned per list objects request | 10000 |
| Maximum number of multipart uploads returned per list multipart uploads request | 1000 |
List of Amazon S3 API's not supported on MinIO
We found the following APIs to be redundant or less useful outside of AWS S3. If you have a different view on any of the APIs we missed, please open a github issue.
List of Amazon S3 Bucket API's not supported on MinIO
- BucketACL (Use bucket policies instead)
- BucketCORS (CORS enabled by default on all buckets for all HTTP verbs)
- BucketReplication (Use
mc mirrorinstead) - BucketWebsite (Use
caddyornginx) - BucketAnalytics, BucketMetrics, BucketLogging (Use bucket notification APIs)
- BucketRequestPayment
List of Amazon S3 Object API's not supported on MinIO
- ObjectACL (Use bucket policies instead)
- ObjectTorrent
Object name restrictions on MinIO
Object names that contain characters ^*|\/&"; are unsupported on Windows and other file systems which do not support filenames with these characters. Note that this list is not exhaustive, and depends on the maintainers of the filesystem itself.