User device requesting map tiles
Cloud / Knowledge library
Amazon CloudFront
Distributes web content and APIs through the AWS edge network
Why learn Amazon CloudFront?
Teams use Amazon CloudFront to adopt content delivery and edge acceleration without building the complete underlying platform themselves.
The problem it solves
Caches and accelerates content through globally distributed edge locations
Where it came from
Amazon CloudFront is Amazon Web Services's offering for content delivery and edge acceleration. Its closest catalog counterparts are Azure Front Door and Google Cloud CDN; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of Amazon CloudFront.
- Choose a workload that fits Amazon CloudFront.
- Identify one operational tradeoff of Amazon CloudFront.
- Compare Amazon CloudFront with Azure Front Door.
- Compare Amazon CloudFront with Google Cloud CDN.
Documentation and sources
- AWS cloud services catalog (aws.amazon.com)
Connect the ideas
Alternatives
Real World Example
Global Media Distribution for Urban Transit Maps
A municipal transit authority providing real-time digital map updates to millions of commuters via mobile applications.
The business problem
The central origin server experiences high latency and connection timeouts during peak morning commute hours as global users simultaneously request large, static map tile assets.
How this topic solves it
Amazon CloudFront acts as a content delivery network, caching map tiles at edge locations closer to the end-users. This offloads traffic from the origin server and serves content from the AWS edge network, ensuring that users receive map data from the nearest geographic point rather than the central server.
- Create a CloudFront distribution and configure the transit authority's origin server as the primary source for map tiles.
- Define cache behaviors to specify how long map tiles should remain in the edge cache before re-validating with the origin.
- Configure the distribution to use HTTPS for secure delivery of map assets to mobile clients.
- Update the mobile application endpoints to point to the CloudFront domain name instead of the direct origin server URL.
Shows how map requests traverse the network from the user to the edge and origin.
CloudFront cache point
Central transit database
- Mobile App → Request Tile → Edge Location
- Edge Location → Deliver Cached Tile → Mobile App
- Edge Location → Fetch Missing Tile → Origin Server
Expected business outcome
Commuters experience faster map loading times and the transit authority's origin server maintains stability by serving only a fraction of the total requests.
Limitations and checks
Cache invalidation is not instantaneous; if map data is updated, users may see stale tiles until the Time-to-Live (TTL) expires or an explicit invalidation request is processed, which can be verified by checking the 'X-Cache' header in HTTP responses.