How emrecancioglu7/aws-cloud-resume works
Project type and purpose
• From the README and file tree, this is a serverless “full-stack” resume website built for the Cloud Resume Challenge.
• The frontend is a static HTML/CSS/JS site (pages, assets, SASS, Bootstrap, custom scripts).
• The backend is a minimal visitor-count API built on AWS Lambda + DynamoDB, fronted by API Gateway.
• Infrastructure and deployments are automated with Terraform and GitHub Actions.
Main system components
a. Frontend (static site)
• Code in index.html, addLater.html, maestro.html, service-details.html, etc.
• CSS (assets/css, css/, sass/) and JS (assets/js, js/) assets/images/fonts
• Hosted on AWS S3 bucket as a static website
• Served via AWS CloudFront CDN
• Custom domain configured in AWS Route 53
• SSL/TLS provided by AWS Certificate Manager
b. Backend (visitor-count API)
• AWS API Gateway (HTTP API) exposing /visitor-count endpoint(s)
• AWS Lambda function (Python) to increment & read a counter
• AWS DynamoDB table to store visitor count
c. CI/CD & IaC
• GitHub Actions workflows (from .github/workflows/main.yml)
• Deploy static files to S3
• Invalidate CloudFront cache
• Terraform code (not shown in file tree) defines S3, CloudFront, Route 53, ACM, API Gateway, Lambda, DynamoDB
d. External Dependencies
• Terraform CLI, AWS provider
Component interactions and data flow
1. User → DNS (Route 53) → CloudFront
2. CloudFront cache hit → S3 (static assets) returns HTML/CSS/JS
3. Browser renders site; JS code calls the API endpoint via API Gateway
4. API Gateway → Lambda → DynamoDB (read/update visitor count) → Lambda response → API Gateway → browser
5. Terraform provisions all resources; GitHub Actions updates the frontend and triggers CloudFront invalidation
Architectural patterns & principles
• Serverless architecture: no host‐managed servers, pay-per-use
• Single-page/static site plus serverless API (micro-service style)
• Infrastructure as Code (declarative, repeatable)
• CI/CD for automated deployments and cache invalidation
• Security best practices:
• Enforce SSL/TLS via ACM & CloudFront
• API Gateway as the only public entry to Lambda/DynamoDB
• Clear component labels (name + purpose)
• Callouts or notes for key design choices (serverless, IaC, CI/CD)