Skip to main content
Limitations of object storage
Last update:

Limitations of object storage

We recommend uploading objects larger than 100 MB using the segmented loading through S3 API or Swift API.

Storage limits and container limits you set up on your own.

Limitations of storage entities

Maximum number of containers in a project2 000*
Maximum number of containers with Virtual-Hosted addressing in a project100 (within 2,000)
Maximum container name size128 UTF-8 characters
Maximum size of the access policy20 KB.
Maximum number of objects in a containerNot limited

* The first 1000 containers are displayed in the dashboard. If there are more containers, you can view the full list through the API.

Limitations of API requests

The limits are for a single container. If your load profile exceeds these limits, we recommend that you distribute the load across multiple containers at a rate of no more than 250 requests per second (RPS) per container.

If the limit is exceeded, the server will return a response with the code 429 Too Many Requests and a message Rate Limit exceeded.

Type of requestsLimit (requests per second)Message from the server
All inquiries2 000Too many authorized requests
GET + HEAD1 000Too many GET requests
POST200Too many POST requests
PUT300Too many PUT requests
DELETE300Too many DELETE requests