CDN

Networking & Edge → CDN (/gravity/cdn) manages content delivery distributions you already have at your cloud provider - Amazon CloudFront, Azure Front Door, Google Cloud CDN, or Cloudflare. It doesn’t create a new distribution for you; it imports and manages one that already exists.

Importing a distribution

1. Click Import Distribution.
2. Choose the provider, then one of your connected credentials for that provider (see Connect a cloud provider if you don’t have one yet).
3. Enter the distribution’s own ID at the provider (for example, a CloudFront distribution ID).
4. Confirm. Sencai reads the distribution’s metadata from your provider account - domains, provider, and status - and adds it to your list.

The distribution list shows each one’s name, provider, domains, and status. Status reflects what the provider itself reports: deployed (live), in progress (a change is still propagating), disabled, or importing (Sencai is still pulling in its metadata).

Note

CDN distributions aren’t tied to Hetzner - there’s no Hetzner CDN adapter, so this screen only has something to import if your connected provider is AWS, Azure, GCP, or Cloudflare.

Managing a distribution

Open a distribution to manage two things:

• Cache Rules - path-pattern-based rules with a TTL, query-string caching mode (cache all query strings, none, or a whitelist), a cookie forwarding setting (all, none, or a whitelist), a compression toggle, and which HTTP methods are allowed. Creating or updating a rule pushes the change to your provider’s cache configuration in the background, in addition to being saved in Sencai. Each rule can also be toggled active or inactive without deleting it.
• Performance - request/traffic metrics pulled live from your provider, with a period selector (1 hour, 24 hours, or 7 days).

Caution

Pushing a cache rule to your provider is best-effort: if that call fails, the rule is still saved in Sencai and the interface does not show an error. That means the rule recorded here and what’s actually configured at your provider can drift apart without an obvious warning. If cache behavior doesn’t seem to match what you configured, check the distribution directly in your provider’s console.

Invalidating cache

Triggering an invalidation sends a purge request to your provider for the paths you specify, clearing cached content so the next request picks up fresh content. Invalidation is provider-side and can take a few minutes to fully propagate across edge locations - don’t assume a change is live everywhere the instant the request completes.

Removing a distribution

Deleting a distribution from this list removes Sencai’s record of it only - the distribution itself keeps running at your provider, still serving traffic under whatever configuration it already had. Use this when you want Sencai to stop tracking a distribution, not as a way to tear one down.

What’s next

• Connect a cloud provider - needed before you can import a distribution
• DNS - the domains a distribution serves are usually managed here
• TLS certificates
• Firewalls & security groups