Custom Domains
A custom domain is a hostname you own, such as assets.example.com, that serves a public bucket instead of the bucket’s test Public Access URL. IBEE gets an HTTPS certificate for the hostname automatically. Use it for production downloads, website assets and links you’ll publish, because the Public Access URL is rate-limited and meant for testing.
When to use a custom domain
How it works
- You create a CNAME record — a DNS entry that says “this hostname is an alias of that one” — pointing your hostname at the target IBEE shows you (it ends in
.ibee.zone). - You add the hostname in the bucket’s Custom Domains tab. IBEE checks that the CNAME already points to the target.
- IBEE gets an HTTPS certificate (from Let’s Encrypt) and starts serving the bucket on your hostname:
https://assets.example.com/OBJECT-KEY.
Before you begin
- A bucket with Public Access turned on. See Bucket Policies → Public access. Every object in a public bucket can be read by anyone.
- Access to your domain’s DNS settings (at your registrar or DNS provider).
- A hostname that isn’t used by another bucket, such as a subdomain like
assets.example.com. - Billing in good standing: custom domains are a separately billed add-on, and the portal checks your billing before it adds one.
Add a custom domain
Open Custom Domains
Open the bucket, click Settings, then Custom Domains, and click Add Domain. The Add Custom Domain dialog says Connect your bucket to a custom domain.
Copy the CNAME target
Step 1 of the dialog reads Add a CNAME record in your DNS pointing to: and shows the target, which ends in .ibee.zone. Click Copy.
Create the CNAME record
At your DNS provider, add a record:
Wait until the record resolves. Check from a terminal:
It should print the target. Most providers publish changes within minutes; some take longer.
Add a custom domain with the API
Create the CNAME first, then:
Remove one with DELETE …/custom-domains/assets.example.com. Scopes: object-storage.read, object-storage.write and, to remove a domain, object-storage.delete.
Verify
The status in the Custom Domains list moves to Active:
Then fetch a file:
HTTP/2 200 means it works. A key that doesn’t exist returns 404.
Remove a custom domain
Click Remove next to the domain, then Remove Domain in the Remove Custom Domain dialog. The hostname stops serving the bucket. Delete the CNAME record at your DNS provider afterwards.
