CDN
A CDN (content delivery network) is a set of servers around the world that keep copies of your files close to your visitors. IBEE CDN lets you put a distribution in front of a public Object Storage bucket: visitors download from the nearest CDN server instead of from the bucket, so pages load faster and the bucket handles fewer requests. Each distribution gets its own address, such as https://dl-abc123.cdn.ibee.ai, with HTTPS included.
When to use the CDN
How it works
- You create a distribution for a public bucket and pick a cache policy. IBEE gives it an address under
cdn.ibee.ai. - The first visitor to ask for a file is a miss: the CDN fetches the file from the bucket, sends it, and keeps a copy.
- Later visitors get the cached copy (a hit) until the copy expires or you purge it. How long a copy is kept is its TTL (time to live).
- Browsers always check back with the CDN before reusing a file they have, so after you purge, visitors get the new version on their next request.
Before you begin
- A verified organization. Until it’s verified, the portal shows Verify Identity instead of Create CDN. See Verify your identity.
- A bucket with Public Access turned on. Private buckets can’t be CDN origins; the bucket picker marks them Private. See Bucket policies → Public Access.
- Room in your plan. Your plan sets how many distributions you can have. See Limits and quotas.
- For your own domain: access to your domain’s DNS settings. Custom domains are billed as an add-on.
- For the API: an API token with CDN permission (
cdn.read,cdn.write) and your workspace ID.
Create a distribution
Open CDN
In the sidebar, under Network & Security, click CDN. The CDN Distributions page opens. With no distributions yet, it shows “No CDN Distributions”.
Open the create dialog
Click Create CDN. The Create CDN Distribution dialog opens: “Configure origin and caching”.
Name it and pick the bucket
Enter a Name (1–128 characters, for example my-cdn-distribution). Under Origin Type, keep Object Storage Bucket and choose your bucket from Select a bucket.
Choose a cache policy
Pick a Cache Policy. Static Assets is the default. See Cache policies for how long each one keeps files.
The dialog also offers Custom Origin (“Use any external HTTPS website or server”), but creating a distribution with a custom origin doesn’t work at the moment. Use an Object Storage bucket.
Each bucket can have one distribution. Custom domains are added after creation, from the distribution’s page.
Cache policies
The cache policy sets two things: how long the CDN keeps a copy (the TTL), and what it tells browsers. It replaces any Cache-Control header stored on your objects.
When you replace or delete a file in the bucket, IBEE queues a purge of the CDN’s copy automatically. If visitors still get the old version, purge it yourself.
To change the policy later, use the API (PATCH /cdn/distributions/DISTRIBUTION-ID with cache_policy). The portal has no edit option.
Verify
-
In the list, the distribution’s Status shows
activewhen it’s ready (deployingwhile IBEE sets it up,failedif setup failed). -
Copy the CDN URL and request a file you know is in the bucket:
The first line should show status
200. Use the object’s key (its path in the bucket) after the address. -
To see hits and misses, open the distribution and click the Metrics tab. Cache hit rate and the Cache statuses breakdown (hit, miss, bypass, dynamic) show how much traffic came from the cache. Data for the latest hours can still be processing; the tab says so.
Custom domains
Serve files from your own address, such as cdn.example.com, instead of dl-abc123.cdn.ibee.ai. The certificate is issued automatically.
Point your DNS at the CDN
At your DNS provider, create a CNAME record from your subdomain to cname.cdn.ibee.ai:
Add the domain
Open the distribution and click Add Domain. In Add Custom Domain, enter the subdomain you pointed at cname.cdn.ibee.ai, then click Add Domain. The portal first checks with billing that the add-on is allowed; if it isn’t, an error explains why.
Add any extra records and wait
The domain card shows Pending while IBEE checks the domain over HTTP and issues the certificate, usually 5–15 minutes and up to 1 hour. If the card lists extra TXT or CNAME records, add them at your DNS provider too. Click Verify on the card to check again (after validation, the button becomes Check Status). When the card shows Active, the domain serves your files over HTTPS.
To remove a domain, click the delete icon on its card. It’s removed straight away, without a confirmation step. Then delete the CNAME record at your DNS provider.
Purge cached content
Purging deletes the CDN’s copies, so the next request fetches the file from the bucket again. Open the distribution and click Purge CDN. In Custom Purge, choose what to purge:
Separate entries with commas or put one per line. Purge Everything needs the box “Yes, I understand. Purge all cached content.” ticked. After a full purge, every file is a miss once, so the bucket gets more requests for a while.
Single-page apps
A single-page app (SPA) is a website, such as a React or Vue app, where one index.html handles every page address. On the distribution’s Overview tab, the Single-page application (SPA) card makes the CDN serve index.html for page addresses, so deep links such as /dashboard/settings load your app. Tick Enable SPA and click Save; untick it and save to turn it off. Requests for missing files still return 404.
Delete a distribution
Deleting a distribution can’t be undone. Its CDN URL stops working; a new distribution gets a different one. Move your DNS records and links first. The bucket and its files are not deleted.
In the CDN list, click the delete icon in the Actions column. In the Delete Distribution dialog, type the distribution’s name and click Delete Distribution.
Use the API
Create a distribution for a bucket (origin_id is the bucket name):
The answer includes id, status and default_url. Purge two files:
Other operations:
