S3 Gateway

S3-compatible gateway

One endpoint. Every cloud you've connected.

The gateway is the addressable surface of your Uploom storage. It speaks the S3 protocol, authenticates every request with AWS Signature V4, and translates each S3 verb into a call against the connected provider that owns the bucket. The gateway itself doesn't store your files — it routes reads and writes through to the cloud account where the data actually lives.

Why an S3 gateway

S3 is the lingua franca of object storage. Every operating system ships tools that speak it, every language has a mature SDK for it, and there are dozens of battle-tested GUI clients. By exposing your multi-cloud storage as an S3 endpoint, Uploom means you don't have to learn a new tool to use it — you keep your stack.

What you can do with it

List, read, write, and delete files across every connected provider using the same client.
Mount all your cloud storage as a single local folder using rclone or Mountain Duck.
Back up and archive data without writing per-provider integrations.
Generate presigned URLs for direct browser uploads and downloads.

What's implemented

All core S3 object verbs: ListObjectsV2, GetObject, PutObject, HeadObject, DeleteObject.
Bucket verbs: ListBuckets, HeadBucket, CreateBucket (no-op), DeleteBucket (no-op).
Multipart upload: CreateMultipartUpload, UploadPart, CompleteMultipartUpload, AbortMultipartUpload, ListParts, ListMultipartUploads.
Presigned URLs (header and query forms of SigV4).

See Supported operations for the full list, and Limitations for what's intentionally not implemented.

Endpoint

The gateway is reachable at https://s3.uploom.io. It accepts any Content-Type on PUT and echoes the value back on GET.

Path-style only

The gateway only supports path-style addressing: https://s3.uploom.io/<bucket>/<key>. Virtual-host addressing is not supported. Configure your client with force_path_style = true (rclone) or addressing_style: path (boto3).

Auth

Every request is signed with AWS Signature V4. The gateway supports both the header form (Authorization: AWS4-HMAC-SHA256 …) and the query form (presigned URLs). See Authentication for details.