/// GUIDES / DIGITALOCEAN CDN

DigitalOcean CDN

For DigitalOcean Spaces buckets, you can manage the edge CDN directly from storafleet — no jumping to the DigitalOcean console — for faster object delivery.

This feature is DigitalOcean Spaces only. The CDN controls appear on Fleets backed by Spaces and aren't available for other providers.

What you can do

Enable / disable the edge CDN for the bucket.
Set the cache TTL that controls how long objects stay cached at the edge.
Attach a custom domain via a CNAME.
Provision a managed TLS certificate, DNS-validated.
Purge cached objects from the edge.
Serve object URLs through the CDN host for faster delivery.

Enable & cache TTL

Turn the CDN on for a Spaces bucket with a single toggle, then set the cache TTL— the time objects are held at the edge before the CDN revalidates them. A higher TTL means fewer trips back to the origin; a lower TTL means changes propagate sooner.

Custom domain & TLS

Attach a custom domain by pointing a CNAME at the CDN, then provision a managed TLS certificate for it. The certificate is DNS-validated, so you prove control of the domain through a DNS record rather than by hosting a file.

Purge & serve through the CDN

When you replace an object and want the change live immediately, purge the cached copies from the edge. To take advantage of the CDN, have storafleet serve object URLs through the CDN host so requests are answered from the edge for faster delivery.

After replacing an object, purge it so visitors get the new version instead of a stale cached copy that lingers until the TTL expires.

PreviousCost & optimization

NextPublic access & policy