minio/docs/minio-limits.md

MinIO Server Limits Per Tenant

For best deployment experience MinIO recommends operating systems RHEL/CentOS 8.x or later, Ubuntu 18.04 LTS or later. These operating systems package the latest 'xfsprogs' that support large scale deployments.

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
Minimum number of drives per server when server count is 1	04
Minimum number of drives per server when server count is 2 or 3	02
Minimum number of drives per server when server count is 4	01
Maximum number of drives per server	no-limit
Read quorum	N/2
Write quorum	N/2+1

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 range	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	1000
Maximum number of multipart uploads returned per list multipart uploads request	1000
Maximum length for bucket names	63
Maximum length for object names	1024
Maximum length for '/' separated object name segment	255

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)
• BucketWebsite (Use caddy or nginx)
• 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 platform or any other file systems that do not support filenames with special charaters. This list is non exhaustive, it depends on the operating system and filesystem under use - please consult your operating system vendor. MinIO recommends using Linux based deployments for production workloads.
• Objects should not have conflicting objects as parents, applications using this behavior should change their behavior and use proper unique keys, for example situations such as following conflicting key patterns are not supported.

PUT <bucketname>/a/b/1.txt
PUT <bucketname>/a/b

PUT <bucketname>/a/b
PUT <bucketname>/a/b/1.txt