Frontend Hosting and Edge Caching
The question for this group
How do users receive the correct frontend release quickly and securely?
Make this your first complete AWS application deployment.
Topics to explore
- Hosting choices: static SPA, static export, server rendering, and managed hosting with Amplify.
- Object hosting: S3 buckets, objects, metadata, private origins, and CloudFront origin access control.
- Edge delivery: CloudFront distributions, origins, behaviors, domains, and HTTPS.
- Cache correctness: Cache-Control, cache keys, asset hashing, HTML freshness, and invalidation.
- Frontend routing: deep links, fallback handling, missing assets, and meaningful HTTP status codes.
- Release consistency: asset upload order, old browser tabs, API compatibility, preview environments, and rollback.
Practice target
Deploy a static frontend through CloudFront with a private S3 origin. Verify a deep link and a new release, then restore the previous release.