Private bucket origin · Amazon S3 & S3-compatible
Point the image CDN at a private Amazon S3, MinIO, Wasabi or Backblaze B2 bucket. Edge nodes sign every GET with AWS Signature Version 4 and deliver AVIF or WebP.
Your bucket stays private. Instead of putting a signing proxy in front of it or opening public read access, you give the console a read-only access key once. Each edge node signs its own GET requests to the bucket over HTTPS, transforms the image into AVIF or WebP at the requested width, and caches the rendition.
Signing: AWS Signature Version 4 (HMAC-SHA256) for service s3 in the bucket's region, with x-amz-content-sha256 set to the empty-payload hash.
| Field | What to give |
|---|---|
| Bucket | The bucket name, such as my-images. Dotted names use path-style URLs so the TLS certificate matches. |
| Region | The bucket's AWS region, such as eu-west-1 or us-east-1. |
| S3-compatible endpoint (optional) | Leave empty for AWS. For MinIO, Wasabi, Backblaze B2 or DigitalOcean Spaces, give the HTTPS endpoint alone, such as https://s3.wasabisys.com. |
| Folder (optional) | A key prefix inside the bucket, such as images/originals. Every delivery path resolves under it. |
| Access key id and secret | An IAM user or key allowed s3:GetObject on arn:aws:s3:::my-images/*. |
The secret is sealed at rest with the Data Protection key ring and never shown back in the console. Rotating credentials means entering a new key on the bucket row; edge nodes pick it up within a minute.
An account can configure up to 10 private buckets and point the account origin or individual custom hostnames at them.
Other private bucket origins: Cloudflare R2 , Google Cloud Storage , Azure Blob Storage .