Static Hosting with S3, CloudFront, and Terraform

This project turns a common cloud pattern into a portfolio-ready case study.

The goal is not to replace Vercel for this blog. The goal is to show that the same static-site idea can be provisioned on AWS using infrastructure as code.

System Shape

User
  -> CloudFront
  -> S3 static origin
  -> Terraform-managed infrastructure

The important part is the explanation around the architecture:

• why S3 is private
• how CloudFront handles caching
• how Terraform manages repeatable infrastructure
• how GitHub Actions can deploy without long-lived AWS keys

Portfolio Angle

This kind of project is useful because it is small, inspectable, and realistic. A hiring manager can read the post, inspect the Terraform code, and understand the design tradeoffs without needing access to private work history.