How naveen359-g/host-resume-on-aws-s3 works
Project Type and Purpose
• This is an infrastructure‐focused, static website hosting project. You’re deploying a simple HTML/CSS/JS “resume” site to AWS S3, fronting it with CloudFront for CDN and HTTPS (via ACM), and managing your custom domain and DNS in Route 53.
File Structure Analysis
• Top level only contains static assets:
• index.html
• styles.css
• script.js
• No application server code—everything is served statically out of S3.
Key Components
a. Client / Browser
b. AWS Route 53 (DNS & domain registration / hosted zone)
c. AWS Certificate Manager (ACM) in us-east-1
d. AWS CloudFront Distribution
e. AWS S3 Bucket (static website hosting)
f. (Optional) ACM DNS validation CNAME record in Route 53
Relationships & Data Flows
1. User enters “yourdomain.com” in the browser.
2. DNS query goes to Route 53 → returns alias record pointing to CloudFront distribution.
3. Browser connects (HTTPS) to CloudFront edge location (SSL terminated with ACM certificate).
4. CloudFront edge checks cache; if miss, it fetches objects from S3 website endpoint origin.
5. CloudFront returns static files (HTML/CSS/JS) to the client over HTTPS.
Architectural Patterns & Principles
• CDN + static site hosting: offload all dynamic logic; scale globally.
• SSL termination at CDN edge: security and performance.
• DNS alias records: tightly integrate Route 53 with AWS resources.
• Infrastructure components are fully managed (no servers) → high availability, low maintenance.