The same static content is delivered worldwide.
Reduce repeated origin access and long-distance transfer.
Which architecture is most appropriate?
Use S3 as the CloudFront origin and cache content at edge locations to reduce origin reads and improve delivery latency.
Detailed explanation
DNS records are not a static-content cache.
DNS records are not a static-content cache.
This increases origin access and transfer rather than optimizing them.
This increases origin access and transfer rather than optimizing them.
CloudFront cache hits reduce origin reads and long-distance delivery for static content.
CloudFront cache hits reduce origin reads and long-distance delivery for static content.
Without a cache, the origin receives repeated requests and distant users see higher latency.
Without a cache, the origin receives repeated requests and distant users see higher latency.
Check official documentation
Compare the following points with the official documentation.
Amazon CloudFrontのS3オリジンとキャッシュの公式説明を確認する。
What to confirm
静的コンテンツの配信経路をCDNとオリジンへ分けて最適化できる。
Key points
- Amazon CloudFront
- S3 origin
- Edge cache
Notes
- Environment: AWS公式CloudFront・S3ドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Origin offload
Cache hits reduce S3 reads and long-distance transfer from the origin.
Cache policy
Caching must reflect content freshness and invalidation requirements while still reducing repeated origin requests.