S3 on Quake AI
Coming from another cloud?
▸AWS·Amazon S3
This Quake AI feature maps to AWS’s Amazon S3.
▸Azure·Blob Storage
This Quake AI feature maps to Azure’s Blob Storage.
▸DigitalOcean·Spaces API (S3-compatible RESTful XML API)
Spaces API (S3-compatible RESTful XML API)
- Spaces documents that it implements only a subset of the Amazon S3 API; migrating users may need to validate specific S3 operations/behaviors they rely on rather than assuming full parity. ().
- Endpoint format is region-based (`${REGION}.digitaloceanspaces.com`) and uses bucket subdomains, which differs from typical OpenStack endpoint discovery (Keystone catalog) and Swift URL layouts. ().
- Spaces supports SigV4 (recommended) and SigV2 (legacy) signing for S3 requests, whereas OpenStack Swift deployments often rely on Keystone tokens for Swift API access (and any S3 compatibility is typically provided via an additional gateway). (, ).
▸Google Cloud·Storage
This Quake AI feature maps to Google Cloud’s Storage.
S3 on Quake AI
Amazon S3 naming is everywhere in tooling, SDKs, and migration guides. On Quake AI, S3-compatible access targets object storage backed by OpenStack Swift with an S3 API gateway. You create buckets (Swift containers), upload objects, and authenticate with S3 credentials or Keystone-derived keys.
The product documentation uses object storage and bucket as primary nouns; S3 describes the API dialect your client speaks.
On Quake AI#
- Endpoint pattern:
https://object.<region>.rumble.cloud(see service endpoints) - Console label: Object storage buckets under the storage section
- CLI/SDK: AWS CLI,
boto3,rclone, and similar tools work when you set the custom endpoint and region - Auth: S3 access keys from the Console; not the same as OpenStack application credentials
S3 compatibility covers the operations most applications need; some AWS-only features (certain lifecycle rules, event notifications, IAM bucket policies) differ or are absent. Validate critical calls against S3 compatibility and the object API reference before cutover.
What other providers call this#
| Provider | Their term | On Quake AI |
|---|---|---|
| AWS | S3 bucket | Object storage bucket |
| Google Cloud | Cloud Storage bucket | Object storage bucket |
| Azure | Blob container | Object storage bucket |
| DigitalOcean | Space | Object storage bucket |
| Hetzner | Object Storage bucket | Object storage bucket |
What to read next#
- Object storage: architecture, access patterns, and Swift relationship
- Create S3 credentials: keys for SDK and CLI access
- Migrate from Amazon S3: rclone and endpoint cutover
Quick answers
- What is the S3-compatible endpoint hostname?CLIAPI
- Where do I set CORS rules, lifecycle policies, or bucket policies in the Console?Console
- Why do Object Storage API curl examples fail before the first request?API
- Why does my public bucket URL return 404 from the browser after I apply a public-read policy?APIConsole
Related content
Pages
How-tos
How to access buckets via FTP, FTPS, or SFTP
Object storage
How to Back Up to Quake AI Object Storage
Object storage
How to create S3 credentials
Object storage
How to Migrate from AWS S3 to Quake AI
Object storage
How to Migrate from Azure blob storage to Quake AI
Object storage
How to Migrate from Backblaze B2 to Quake AI
Object storage
How to Migrate from DigitalOcean Spaces to Quake AI
Object storage
How to Migrate from Google Cloud storage to Quake AI
Object storage
How to Migrate from Hetzner object storage to Quake AI
Object storage
How to Migrate from Linode object storage to Quake AI
Object storage
How to Migrate from Vultr object storage to Quake AI
Object storage
How to Migrate from Wasabi to Quake AI
Object storage
How to mount S3 storage on Windows, macOS, and Linux
Object storage
How to Set Up Multi-Cloud Object Storage Sync
Object storage
How to Update Your Application's S3 Endpoint for Quake AI
Object storage
Tutorials
Explanations
Reference
troubleshooting