Users worldwide request the same images and static files.
Reduce origin requests and long-distance data transfer.
Which service is most appropriate?
Use CloudFront edge caching so content can be served near users instead of fetched from the origin for every request.
Detailed explanation
DNS records are not a static-content cache.
DNS records are not a static-content cache.
IAM policies do not change data-transfer pricing.
IAM policies do not change data-transfer pricing.
Edge locations cache content near users and reduce origin fetches and latency.
Edge locations cache content near users and reduce origin fetches and latency.
Without caching, origin load and transfer volume increase.
Without caching, origin load and transfer volume increase.
Check official documentation
Compare the following points with the official documentation.
Amazon CloudFront cachingと料金の公式説明を確認する。
What to confirm
エッジキャッシュによるオリジン負荷・転送量削減を説明できる。
Key points
- CloudFront
- Edge cache
- Cache hit ratio
Notes
- Environment: AWS公式CloudFrontドキュメントの確認
- Confirm current AWS service behavior and pricing in the official documentation.
Foundation review
Origin offload
A higher cache hit ratio reduces origin requests, latency, and some transfer paths.
CDN versus DNS
A CDN caches content; DNS routing only selects or resolves a name.