What you declare for cached delivery
A public site or asset prefix is a gateway route of type prefix. Set cdn_enabled to true on that route when the files should be cached. The target is a bucket in the same project, and default_key names the document for a directory path, usually index.html.
kernstack plan shows the route before it is published. The cache sits on hardware we operate in Europe. Egress is 9.00 credits per GiB, and bucket storage is 0.04 credits per GB-hour. There is no separate CloudFront account.
What stays behind in CloudFront
Nothing in the route is a translation of a CloudFront distribution. Behaviors, origin groups, cache policies, origin request policies, CloudFront functions, and Lambda@Edge associations are not read and not written into stack.json.
You name the route, the bucket, and whether the CDN is on. Viewers request the gateway hostname. They do not inherit a CloudFront domain, a price class, or a geographic restriction list from an exported configuration.
Amazon CloudFront vs KERNSTACK on European Bare Metal
| Dimension | Amazon CloudFront | KERNSTACK CDN |
|---|---|---|
| Operator | AWS account | KERNSTACK project |
| Manifest | Amazon CloudFront console or API | prefix route, cdn_enabled true |
| Region | AWS region list | European bare metal |
| Bill | Amazon CloudFront line item | One project credit balance |
Frequently asked questions
No. You declare a prefix route and set cdn_enabled. Distributions, behaviors, origins, and cache policies are not copied into stack.json.
On the gateway route. A prefix route targets a bucket and can name a default document. cdn_enabled turns on cached delivery for that route.
Bucket storage is 0.04 credits per GB-hour. Egress is 9.00 credits per GiB. Both draw from the project credit balance.
Related capabilities, architectures, and comparisons
Ship your stack on the Software Lifecycle Cloud.
Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.