CDN Integration | ibee | Documentation

A CDN distribution puts a global cache in front of your Object Storage bucket. Static files, media, and other assets are served from edge nodes closer to your users — reducing latency and origin load. Your CDN URL is assigned automatically in the format dl-{hash}.cdn.ibee.ai.

Before you begin

An active IBEE Cloud project (Create a project)
An Object Storage bucket with files to distribute (Create a bucket)

1. Go to CDN

In the IBEE Cloud portal, click CDN in the left sidebar under Infrastructure.

2. Create a distribution

Click + Create CDN. If no distributions exist yet, the empty state shows a create prompt — click it to proceed.

3. Configure the distribution

Fill in the fields in the Create CDN Distribution panel:

Field	Required	Notes
Name	Yes	e.g., `my-cdn-distribution`
Origin Type	Yes	Object Storage Bucket or Custom Origin
Cache Policy	No	Defaults to Static Assets

Origin Type options:

Object Storage Bucket — Select an existing bucket from your account as the origin.
Custom Origin — Use any external HTTPS website or server. Enter an IP address or domain name (e.g., api.example.com or 192.168.1.100) and a Port (default: 443).

Cache Policy options:

Policy	TTL	Best for
Static Assets	1 year	Images, fonts, CSS, JS
Media Files	30 days	Video and audio
Short Cache	1 hour	Frequently changing content
No Cache	None	Always fetches from origin

Custom domains and SSL Custom domains can be added after the distribution is created. SSL certificates are automatically provisioned — no manual configuration required.

4. Create the distribution

Click Create Distribution. The distribution is provisioned and assigned a CDN URL in the format dl-{hash}.cdn.ibee.ai.

Verify

Your new distribution appears in the CDN list with these columns:

Column	Description
NAME	Distribution name
ORIGIN	Source bucket or custom origin
CDN URL	Assigned URL — `dl-{hash}.cdn.ibee.ai`
CACHE POLICY	Selected caching behavior
STATUS	Active
ACTIONS	Delete

Copy the CDN URL and use it to serve your assets.

Troubleshooting

Distribution not serving updated content CDN nodes cache content based on the selected policy TTL. To force a refresh, use the No Cache policy or delete and recreate the distribution.

Custom origin not reachable Ensure your custom origin is publicly accessible over HTTPS on the specified port. The CDN requires a valid HTTPS endpoint — HTTP-only origins are not supported.

Cannot add a custom domain during creation Custom domains can only be added after the distribution is created. Create the distribution first, then configure your custom domain from the distribution settings.

SSL certificate not provisioning SSL certificates are automatically provisioned after creation. Allow a few minutes for provisioning to complete before testing HTTPS access.