How osiamaefule.com is wired
A visitor never touches the S3 bucket. Route 53 sends them to CloudFront, and CloudFront reads the private bucket on their behalf. Terraform defines all of it, and one deploy script publishes new files.
What happens when someone opens the site
How changes get to AWS
no-cache headers, then invalidates CloudFront.What each piece does
| Piece | Job | Defined in |
|---|---|---|
| Route 53 | Points osiamaefule.com and www at CloudFront. The hosted zone is only looked up, so its nameservers at Porkbun stay stable. | DNS configuration |
| ACM | Issues the HTTPS certificate and renews it by itself, using CNAME records that must stay in Route 53. | DNS configuration |
| CloudFront | Caches files worldwide, redirects http to https (TLS 1.3 minimum), and shows a custom 404 page for missing pages. | CDN configuration |
| S3 bucket | Stores the files. Every form of public access is blocked, and only this CloudFront distribution may read it. | Storage configuration |
| Deploy script | Checks the AWS login, stamps asset versions, uploads the site files to S3 with no-cache, and invalidates CloudFront. | Automation script |
| State bucket | Holds Terraform's record of what it manages. Created by hand and not managed by Terraform. | Backend configuration |
Hosted zone Z1030602FUNDV4FNUNEX · Region us-east-1 (CloudFront certificates must live there).