S3 Gateway
Limitations
The gateway is a thin protocol adapter, not a re-implementation of S3. Many features are not implemented because Uploom's model is intentionally simpler than AWS S3 — you don't manage buckets, your connections are your buckets.
Hard limits
| Limit | Value |
|---|---|
| Single-part object size | 5 GB |
| Multipart parts | 10 000 per upload |
| Key length | 1024 bytes |
| Bucket name length | 63 chars |
| Presigned URL expiry | 7 days (604800s) |
| Presign rate limit | 60 req/min/token |
Not implemented
- Range requests — the gateway streams whole objects. Range-based reads are not supported.
- If-Match / If-None-Match — no conditional GETs.
- CopyObject — not implemented. Use the dashboard's cross-bucket move action instead.
- Object versioning — the gateway returns
Suspended. - ACLs and policies — buckets always have a single owner (you) with full control. No per-object grants.
- Server-side encryption (SSE-S3, SSE-KMS, SSE-C) — the gateway doesn't negotiate encryption; data is stored on the provider with the provider's default settings.
- Tagging — no
PutObjectTagging/GetObjectTagging. - Event notifications — no SQS/SNS integration.
Why these limits exist
A full S3 re-implementation with IAM, versioning, replication, and lifecycle policies would be a different (and much larger) product. v1 focuses on the most-requested verbs: list, get, put, delete, multipart, and presigned URLs.