CI/CD Pipeline for a Static Website

Tech Stack

Git & GitHub · GitHub Actions · AWS S3 · AWS CloudFront · AWS ACM · AWS Route 53 · AWS IAM (OIDC) · AWS CloudWatch · Bash / YAML

Architecture

Developer → git push (main)
   ↓
GitHub Actions (OIDC auth, sanity check, aws s3 sync)
   ↓
S3 Bucket (private, Block Public Access)
   ↓
CloudFront (HTTPS via ACM, Origin Access Control)
   ↓
Custom Domain → End User

Monitoring: CloudFront access logs → S3, CloudWatch alarm on 5xxErrorRate → email alert.

What This Project Demonstrates

CI/CD pipeline design and GitHub Actions workflow authoring
Secure cloud authentication using OIDC federation instead of static credentials
AWS infrastructure: S3, CloudFront, ACM, Route 53, IAM, CloudWatch
Rollback and failure-prevention strategy, tested rather than just configured
DNS architecture, including cross-account subdomain delegation
Real incident response - a live post-launch outage, diagnosed and resolved
Clear technical documentation, written checkpoint by checkpoint as the project progressed

Explore the Project

Section	What's inside
Progress Tracker	25-day status at a glance
Day 1–3: Git Basics	Repo setup, branch/PR/merge workflow
Day 4–6: Static Site	HTML/CSS build
Day 7–10: GitHub Actions + OIDC	Core CI/CD build - includes full troubleshooting log
Day 11–14: Deploy Verification	End-to-end pipeline testing
Day 15–17: Rollback Strategy	Versioning, git revert, pre-deploy checks
Day 18–20: Custom Domain & HTTPS	CloudFront, ACM, private bucket, DNS delegation
Day 21–22: Log Monitoring	CloudWatch alarms, access logs
Day 23–25: Polish, Docs & Review	README, final review, lessons learned
Post-Launch Incident: DNS Outage	A real production issue, diagnosed and fixed live