Private bucket origin · Amazon S3 & S3-compatible

Serve images from a private S3 bucket

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.

How it works

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.

# Public delivery URL
https://a3f9c21b.zwcld.net/v1/products/sofa.jpg?w=800&f=auto&q=auto
# Signed fetch by the edge node
GET https://my-images.s3.eu-west-1.amazonaws.com/products/sofa.jpg

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.

What the console asks for

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.

Setting it up, step by step

  1. Create an IAM access key with s3:GetObject on the bucket (or a read-only application key on your S3-compatible store).
  2. In the console, open the Domains tab, expand Add a private bucket under Origin, and choose Amazon S3 or S3-compatible.
  3. Enter the bucket name, region, optional endpoint and folder, and the access key id and secret.
  4. Tick Make it this account's origin (or assign the bucket to a single verified custom domain) and save.

Details worth knowing

  • Without s3:ListBucket, an S3 bucket answers a missing object with 403 rather than 404. The edge passes that refusal through and notes that either the credentials lack read permission or the object does not exist.
  • Object keys are escaped per RFC 3986 one path segment at a time (+ becomes %2B, spaces become %20) so the path on the wire matches what SigV4 signed.
  • Conditional revalidation (If-None-Match and If-Modified-Since) is passed through to the bucket, so an unchanged original answers 304 without a second download.
  • Static access keys only; AWS IAM role assumption (STS AssumeRole) is not used.

Connect your bucket

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 .