How abhi-indra/devops_projects_zero_to_hero works
Project type and purpose
• From the file tree and README we see multiple “DevOps_To_Hero_Projects,” each independent. Among them, Project-6 (“Deployment of a ToDo application on AWS using AWS ECR and ECS Fargate”) is the most end-to-end system: a Dockerized Node.js web app, built by Jenkins, pushed to ECR, and deployed on ECS Fargate in AWS.
File structure for Project-6
• Top-level “project-6/” contains a README and a “node-todo-app/” subfolder.
• “node-todo-app/” holds:
• app.js, test.js, views/*.ejs → Node.js + EJS views (web server + UI)
• package.json/lock → dependencies
• Dockerfile & docker-compose.yaml → container build and local compose
• Jenkinsfile → CI/CD pipeline definition
• .gitignore → untracked files
Key insights from the README
• Purpose: demonstrate CI/CD pipeline for a web app using Jenkins, containerization with Docker, image storage in AWS ECR, and runtime on AWS ECS Fargate.
• No external DB shown; assume in-memory or file storage.
Main components
a. Developer environment
• Local workstation or GitHub repo (source code)
b. CI/CD pipeline
• Jenkins server (freestyle or master/agent)
• Jenkinsfile stages: checkout → build Docker image → run tests → push to AWS ECR
c. Container Registry
• AWS ECR repository holding versioned Docker images
d. AWS Networking & Compute
• VPC with public and private subnets
• Application Load Balancer (ALB) in public subnet
• ECS Cluster with Fargate tasks (Node.js containers) in private subnets
• Security Groups controlling inbound (HTTP) and outbound (internet/ECR pull)
e. (Optional) Monitoring & Logging
• CloudWatch Logs for container stdout/stderr
• CloudWatch alarms on task failures or high latency
Relationships & interactions
• Developers commit code → GitHub
• Jenkins polls/triggers on commit → Jenkins pulls code → builds Docker image → runs test.js → on success pushes image to ECR
• ECR stores image → ECS service (Fargate) pulls new image → ALB routes HTTP requests to running tasks
• ALB health-checks tasks → scales tasks based on target tracking or manual configuration
Architectural patterns & principles
• CI/CD (continuous integration and delivery) pipeline
• Immutable infrastructure (Docker images versioned in ECR)
• Serverless container runtime (ECS Fargate)
• Micro-VM isolation per task (one container = one Fargate task)