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

Visitor browser Route 53 DNS records CloudFront cache + HTTPS ACM HTTPS certificate S3 bucket private, no public access ① DNS lookup ② alias A / AAAA points at CloudFront ③ HTTPS request ④ only on cache miss: signed read (OAC) certificate
Steps 1 and 2 happen before the page loads: the browser asks Route 53 where the domain points, and the record answers with CloudFront. Step 4 only runs when CloudFront has no cached copy. Otherwise it answers on its own, which is why every deploy also clears CloudFront's cache.

How changes get to AWS

Your laptop code + site files Terraform infrastructure code Terraform state S3: osi-amaefule-tfstate The AWS setup S3 · CloudFront · ACM · Route 53 S3 bucket osi-amaefule-portfolio CloudFront E13O2IELZX6CO0 terraform apply creates / updates state + lock deploy script: upload site files origin deploy script: clear CDN cache
Two separate paths. Terraform changes the infrastructure and never touches your files. The deploy script changes the files and never touches the infrastructure. It stamps a version on the CSS, JS and image links (so browsers never reuse a stale copy), uploads with no-cache headers, then invalidates CloudFront.

What each piece does

PieceJobDefined in
Route 53Points osiamaefule.com and www at CloudFront. The hosted zone is only looked up, so its nameservers at Porkbun stay stable.DNS configuration
ACMIssues the HTTPS certificate and renews it by itself, using CNAME records that must stay in Route 53.DNS configuration
CloudFrontCaches files worldwide, redirects http to https (TLS 1.3 minimum), and shows a custom 404 page for missing pages.CDN configuration
S3 bucketStores the files. Every form of public access is blocked, and only this CloudFront distribution may read it.Storage configuration
Deploy scriptChecks the AWS login, stamps asset versions, uploads the site files to S3 with no-cache, and invalidates CloudFront.Automation script
State bucketHolds 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).