Private bucket origin · Azure Blob Storage

Serve images from a private Azure Blob container

Connect a private Azure Blob Storage container as your image CDN origin. Edge nodes sign each fetch with Shared Key authentication and serve AVIF or WebP.

How it works

For Azure Blob Storage, edge nodes fetch from https://<account>.blob.core.windows.net/<container>/ and sign every GET request with Azure's Shared Key scheme (HMAC-SHA256 over the canonicalised headers and resource, including conditional headers on revalidation). The container's public access level can stay set to Private.

# 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://acct.blob.core.windows.net/my-images/products/sofa.jpg

Signing: Azure Storage Shared Key (HMAC-SHA256) with x-ms-version: 2021-08-06, signing If-None-Match and If-Modified-Since on cache revalidation.

What the console asks for

Field What to give
Container The Blob container name, such as my-images.
Storage account The 3 to 24 character lowercase storage account name.
Folder (optional) A virtual directory prefix inside the container, such as images/originals.
Storage account key One of the storage account's base64 access keys, from Security + networking → Access keys.

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. Put your images in a dedicated Azure storage account with the container's anonymous access level set to Private.
  2. In the Azure portal, open Security + networking → Access keys on that storage account and copy one of the base64 keys.
  3. In the ZawCloud console, open the Domains tab → Add a private bucket, choose Azure Blob Storage, and enter the container name, storage account name and key.
  4. Assign the container as the origin for your account or for a verified custom hostname.

Details worth knowing

  • Azure Shared Key is scoped to the whole storage account rather than to one container. Put images in a storage account of their own so the key cannot read unrelated containers.
  • SAS tokens and Microsoft Entra ID are not supported yet; use one of the storage account's two Shared Keys, and use the second key to rotate without downtime.
  • Revalidation headers (If-None-Match, If-Modified-Since) are included in their fixed positions in the Shared Key string-to-sign, so 304 checks work against private containers.

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: Amazon S3 & S3-compatible , Cloudflare R2 , Google Cloud Storage .