CloudFront Edge

For content delivery and edge compute, AtfCloudFront builds a distribution with a cache policy and optional logging, and the EdgeStack deploys Lambda@Edge functions.

The us-east-1 constraint

Lambda@Edge functions must deploy to us-east-1 — CloudFront replicates them from there to every edge location. The EdgeStack is built for this: instantiate it with env: { ...env, region: "us-east-1" }. This is a hard AWS constraint, not an Axis choice, and the framework surfaces it in the generated stack file’s comments.

Distribution basics

AtfCloudFront takes an originDomain (typically your API’s domain) and builds a cache policy + distribution. Optional logBucketName configures access logging against an imported bucket. Optional domainAliases create an imported ACM certificate for custom domains.

Edge lambda kind

Edge functions use kind: "edge" in their config. The factory omits a managed log group for edge functions — CloudFront manages their logging.

axs add lambda viewer/rewrite --kind edge

Where to go next

• AtfCloudFront for the construct props.
• Lambda Runtimes & the Factory for how edge functions differ.