//
Search across all documentation pages
7 pages in this section.
Where CloudFront sits in a request path: origins, cache behaviors, cache keys, and the edge-cache lifecycle that decides whether a request is served from an edge location or forwarded to your origin.
Hands-on CloudFront basics: create the client, create a distribution in front of an S3 or ALB origin with a managed cache policy, read its status, list distributions, and do the read-config-then-update dance.
Route requests to different origins by path with ordered cache behaviors, and add origin failover with an origin group - all via the CloudFront SDK's DistributionConfig.
Force cached objects out with CreateInvalidation, track completion, understand the free-tier and per-path billing, and why versioned URLs are the cheaper default for cache-busting.
The CloudFront SDK habits that keep hit rates high and bills low: design a tight cache key, prefer versioned URLs over invalidations, always read config before update, lock origins with OAC, and use managed policies.