CDN Integration
A CDN (content delivery network) is a set of servers around the world that keep copies of your files, so users download them from a nearby server instead of from the bucket every time. Putting the IBEE CDN in front of a bucket makes public files load faster, takes load off the bucket, and gives you an HTTPS address and an optional custom domain. This page covers the Object Storage side; the full CDN reference is Network & Security → CDN.
When to use the CDN
How it works
- You create a distribution — a CDN configuration — with the bucket as its origin (where the CDN fetches files from).
- The first request for a file goes to the bucket; the CDN stores a copy for as long as the cache policy says.
- Later requests are answered from the cache at
https://dl-….cdn.ibee.ai/OBJECT-KEY, or your own domain.
Before you begin
- A bucket with the files to serve and Public Access turned on. See Bucket Policies → Public access. The bucket picker marks private buckets Private.
- Billing set up: the CDN is billed separately. See Network & Security → CDN.
- For a custom domain: access to your DNS settings.
Put the CDN in front of a bucket
Choose a cache policy
A changed file isn’t seen by users until its cached copy expires or you purge it. With Static Assets, give each new version a new file name, or purge after you upload.
Use your own domain
To serve the CDN from cdn.example.com, create a CNAME record from your subdomain to cname.cdn.ibee.ai, then click Add Domain on the distribution’s page. See CDN → Custom domains.
Don’t put the same hostname on the bucket’s own Custom Domains tab. A bucket custom domain serves files directly from the bucket and skips the CDN cache.
Verify
Request a file twice through the CDN URL:
HTTP/2 200 means the CDN reached the bucket. The distribution’s Metrics tab shows requests, Data delivered and Cache hit rate — the share of requests answered from the cache.
Update or purge cached files
After you replace a file in the bucket, click Purge CDN on the distribution’s page to remove the cached copy by URL or prefix, or Purge Everything. Purging everything briefly increases load on the bucket while the cache refills. See CDN → Purge cached content.
