Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Deploy a static website on AWS: store the files in an S3 bucket (kept PRIVATE — no public bucket), serve them over HTTPS through a CloudFront distribution using an Origin Access Control so only CloudFront can read the bucket, and (optionally) point a Route 53 domain at it. Stay within the Free Tier and tear everything down afterward. Document the request path: browser → CloudFront edge → S3 origin.
Site served via CloudFront over HTTPS; the S3 bucket is private and reachable only through CloudFront (OAC), not public.
No public bucket; least-privilege bucket policy; understands why a public S3 site is discouraged.
Stays within the Free Tier; resources torn down or documented; no surprise spend.
Can explain the edge-cache → origin request path and why CloudFront beats serving S3 directly.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Host a static site on S3 + CloudFront ## Goal Deploy a static website on AWS: store the files in an S3 bucket (kept PRIVATE — no public bucket), serve them over HTTPS through a CloudFront distribution using an Origin Access Control so only CloudFront can read the bucket, and (optionally) point a Route 53 domain at it. Stay within the Free Tier and tear everything down afterward. Document the request path: browser → CloudFront edge → S3 origin. ## Acceptance criteria - [ ] S3 + CloudFront: Site served via CloudFront over HTTPS; the S3 bucket is private and reachable only through CloudFront (OAC), not public. - [ ] Access & security: No public bucket; least-privilege bucket policy; understands why a public S3 site is discouraged. - [ ] Cost discipline: Stays within the Free Tier; resources torn down or documented; no surprise spend. - [ ] Understanding: Can explain the edge-cache → origin request path and why CloudFront beats serving S3 directly. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.