How bhaskar-2001/website-aws-auto-scaling-deployment works
This repository combines a static portfolio site with its documented AWS deployment workflow. A push to GitHub triggers the Jenkins pipeline in Jenkinsfile; Jenkins syncs the site to S3 and dispatches an SSM command to deploy it across the running EC2 fleet. Users reach the site through the Application Load Balancer and Nginx. The README also describes fleet provisioning and CPU-based scaling. No source excerpts were available, so relationships below are based on README documentation only.
Main entry points: Jenkinsfile Deployment Pipeline · index.html Portfolio Page
Components 13
Portfolio Site
- Portfolio Page
index.html
Deployment
- Jenkins
- Deployment Pipeline
Jenkinsfile - S3 Bucket
- SSM Run Command
Compute and Scaling
- Auto Scaling Group
- Launch Template
- CloudWatch Alarms
- EC2 Fleet
- Nginx
Public Access
- Application Load Balancer
Other components
- GitHub
- End Users
Connections 13
- GitHub → Jenkins: webhook triggers
README.md - Jenkins → Deployment Pipeline: runs pipeline
README.md - Deployment Pipeline → S3 Bucket: syncs site
README.md - Deployment Pipeline → SSM Run Command: dispatches command
README.md - SSM Run Command → EC2 Fleet: deploys files
README.md - EC2 Fleet → S3 Bucket: reads site files
README.md - Auto Scaling Group → Launch Template: launches instances
README.md - Launch Template → EC2 Fleet: configures instances
README.md - CloudWatch Alarms → Auto Scaling Group: triggers scaling
README.md - End Users → Application Load Balancer: HTTP requests
README.md - Application Load Balancer → Nginx: routes requests
README.md - Nginx → Portfolio Page: serves page
README.md - EC2 Fleet → Application Load Balancer: registers targets
README.md