Limits and compatibility
Check this page when you plan an application or migrate from another S3 provider.
Limits
| Item | Limit |
|---|---|
| Object size, single upload | 5 GB |
| Object size, multipart upload | 5 TB |
| Object key (name) length | 1024 bytes (UTF-8) |
| Bucket name | 3–63 characters: lowercase letters, numbers, hyphens and periods; starts and ends with a letter or number |
| Access key pairs per S3 user | 2 (the last pair can't be deleted) |
| Bucket policies per bucket | 1 (with any number of statements) |
| Bucket deletion | Only when empty |
Bucket policy changes are eventually consistent. Allow a short time before testing a change.
Protocol
| API | Amazon S3 REST API |
| Signature | Version 4 (recommended) and Version 2 |
| Addressing | Path-style: https://<endpoint>/<bucket>/<key> |
| Region name | Not checked. Use us-east-1 in tools that require one. |
| Authentication | Header, presigned URL (query string) and browser POST uploads |
Supported features
- Buckets, objects and folders (prefixes)
- Multipart upload
- Presigned URLs
- Bucket policies and ACLs
- Versioning
- Object Lock: retention (Governance and Compliance) and legal hold
- Lifecycle rules: expiration only
- Cross-region replication
- CORS
- Server access logging
- Bucket notifications
- Data integrity checks
Not supported
| Amazon S3 feature | Alternative |
|---|---|
| Storage classes and lifecycle transitions | All data is stored in the same way. Use expiration rules to delete data. |
| Server-side encryption (SSE-S3, SSE-C, SSE-KMS) | Data is encrypted at rest by the platform. For your own keys, encrypt before upload. |
| Lifecycle filters by tag | Filter by prefix |
| IAM users, roles and STS temporary credentials | Use separate S3 users with bucket policies |
| S3 Select | Download the object and process it locally |
Separate Object Lock actions in bucket policies (s3:PutObjectRetention, s3:BypassGovernanceRetention, …) | Use the Object Lock condition keys on s3:PutObject |