Limitations
Cloud Storage, as an implementation of object storage based on OpenStack Swift, has the following limitations:
| Type | Value | Description |
|---|---|---|
| Maximum object size | 5 GB | Maximum size of a single object. Larger files require multipart upload with segmentation and merging |
| Minimum object size | No limitations | While objects with a zero-byte body can be stored, there is metadata and object storage-specific overhead. As a result, the actual minimum storable object size, including overhead, is typically around 4 KB per object. |
| Segment size for multipart uploads | Up to 5 GB | Recommended size for each segment in a multipart upload |
| Maximum number of containers per account | No limitations | |
| Maximum objects per container | Soft limit of 1000000 objects | While there is no hard limit on the number of objects in a container, keep in mind that once a container holds approximately 1 million objects, the operation speed for that container may gradually decrease. |
| Maximum object name length | 1024 bytes | Maximum length of an object name |
| Maximum container name length | 256 bytes | Maximum length of a container name |
| API request limits (GET/PUT/POST/DELETE) | No limitations | Requests to Swift have no limitations, while requests to Keystone (authorization) are limited to approximately 12 RPS. The request capacity depends on the capabilities of the frontend servers, which vary by location (typically two servers) |
| Metadata size | 8 KB | Combined size of all metadata for a single object |
| Metadata entries per object | 90 | |
| HTTP header size | 8 KB | Maximum total size of all HTTP headers in a request |
| Number of object versions | No limitations | |
| Container size | No limitations |