Limits and Quotas
Quotas
| Usage | Limit | AWS S3 equivalent |
|---|---|---|
| Maximum number of buckets | 20 | 100 |
Limits
The following table shows which limits are applied to SOS compared to AWS.
| Usage | Limit | AWS S3 equivalent |
|---|---|---|
| Maximum object size | 4TiB | 5TiB |
| Maximum number of parts in a multipart upload | 10000 | 10000 |
| Minimum part size | 5MiB * | 5MiB * |
| Maximum part size | 5GiB | 5GiB |
| Maximum number of objects in a bucket | unlimited | unlimited |
| Maximum number of versions per object | 1000 | unlimited |
| Minimum billed size | 128kb | 128kb |
| Maximum metadata size | 2kb | 2kb |
| Maximum tags per object | 10 | 10 |
| Maximum tag key size | 128 char | 128 char |
| Maximum tag value size | 256 char | 256 char |
| Maximum bucket name size | 64 char ** | 64 char ** |
| Maximum key name size | 1024 byte (UTF-8) | 1024 byte (UTF-8) |
| Maximum number of objects per delete-objects operation | 1000 | 1000 |
*) does not apply to the ’last part’ **) DNS compatible
Unsupported S3 Features
While we strive to maintain full compatibility with the S3 API, we do not support all S3 features.
Currently, the following functionality cannot be used on Exoscale:
- Object Tagging
- Object Lifecycle Management
- Bucket Access Logging
- Bucket Event Notification
- Static Website Hosting
Availability
Object storage is available in all zones.
Last updated on