Status
What the gateway covers when enabled
The gateway speaks SigV4 and supports:
Multipart limits follow S3 conventions: up to 10,000 parts, up to 5 GiB per part, non-final parts at least 5 MiB, ascending part order, verified ETags, and plan upload caps enforced at initiation and completion.
Objects uploaded through the gateway go through the same encryption pipeline as REST uploads. The stored object is identical to a single-request upload of the same content.
Clients that can work
With the gateway enabled, tools such as rclone, restic, Duplicati, and Borg (via rclone serve) have been validated. Native multipart means the upload cutoff workaround is no longer required, though it remains supported. Do not generalize from this list to “any S3 client works”. Test your specific client against an enabled account.Credentials
The gateway uses SigV4 with the unified API key pair. Scopes still apply:
A key restricted to specific buckets remains restricted through the gateway.
Errors
Gateway errors use standard S3 XML error responses, not the JSON envelopes used by the REST API. If your client handles both surfaces, decode them separately. Common S3 error conditions you may see:Operational notes
- In-progress multipart uploads are tracked with a TTL and cleaned up when they expire.
- An upload initiated by one key cannot be completed or aborted by another key.
- Server disk must accommodate in-flight parts for large multipart uploads.
- Bandwidth quotas apply.
Deciding whether to use it
Related
Status
Capability availability.
Integration overview
All supported paths.
Buckets
Bucket scope and retention.
Support
Confirm gateway availability.