Skip to main content
A distribution is the CDN endpoint your users hit. It maps a hostname to one or more origins, applies cache and access rules, and serves traffic from edge PoPs.

​
Prerequisites

  • A reachable origin (HTTPS hostname, IP, or S3-compatible bucket).
  • DNS access if you plan to use a custom domain (you’ll add a CNAME).
  • An API token if creating distributions from CI/CD.

​
Steps

1

Name the distribution

Use a clear, environment-prefixed name (prod-web, staging-images). Names show up in audit logs and metrics.
2

Choose a domain type

System-generated for quick tests, custom domain for production.
3

Pick a cache strategy

Static, VOD, livestream, or dynamic — sets sensible TTL defaults you can override later.
4

Connect an origin

Hostname, IP, or S3-compatible bucket.
5

Configure advanced settings

Custom Host header for virtual-hosted origins.
6

Verify with curl

curl -I the distribution domain and confirm a 200.

​
Domain type

Domain Type

Domain Type

For a custom domain, create a DNS record like:
Issue an SSL cert in SSL before going live.

​
Cache strategy

Cache Strategy

Cache Strategy

The strategy seeds defaults; you can still add fine-grained cache rules per path.

​
Origin

The origin is the upstream the CDN pulls from on cache miss. Pick one of two types.

​
Hostname origin

Hostname Origin

Hostname Origin

  • Origin Label — internal name.
  • Hostname / IP — must be reachable over HTTPS or HTTP.

​
S3-compatible origin

S3 Bucket Origin

S3 Bucket Origin

  • Origin Label — internal name.
  • Hostname — endpoint of the S3-compatible service (e.g. s3.amazonaws.com, s3.us-east-1.amazonaws.com, nyc3.digitaloceanspaces.com).
  • Access Key ID / Secret Access Key — credentials with read access to the bucket.
  • Bucket — bucket name.
  • Region — bucket region.
Use a read-only IAM user/key. Never reuse a key with write or delete permissions. Rotate the key periodically — Tenbyte’s signed-fetch logic handles rotation transparently if you update both fields together.
Verify the origin can be read with the same credentials:

​
Advanced settings

Advanced Settings

Advanced Settings

The Host header is what the origin sees in Host:. Set it explicitly when:
  • Your origin uses virtual hosting (multiple sites on one IP).
  • The origin’s TLS cert is issued for a specific hostname.
  • A reverse proxy or load balancer routes by Host.

​
Verify the distribution

Expected:
Repeat the call. x-cache should flip to HIT.

​
Create via API

See the CDN API reference for the full schema and updated field names.

​
Common pitfalls