Capstone
Cloud & DevOps
Cloud-Native CI/CD Platform
GitOps pipeline with Kubernetes, Helm and progressive delivery
- Kubernetes
- Docker
- Helm
- Argo CD
- +2
₹5,299₹8,999
4.8/74 reviews
Cloud & DevOps · Major Project
Blue-Green Deployments on AWS ECS
Fargate releases switched over by CodeDeploy, and rolled back on failure
3-4 weeks build
Overview
Two copies of the app, and a load balancer that decides which one is live. A Node.js service runs on ECS Fargate, CodeDeploy brings up the new version beside the old one, test traffic hits it on a separate listener, and the switch happens only once health checks pass. A failing alarm sends traffic straight back. Demo runs are short and a teardown script keeps them within new-account or student credits.
What makes it stand up
- 01New task set started beside the old one, never in place
- 02Test listener so a release is checked before users see it
- 03Cutover gated on target-group health checks and lifecycle hooks
- 04Automatic rollback when a CloudWatch alarm fires after the switch
- 05Short demo runs and a teardown script to protect student credits
Module breakdown
- 01
Container
Node.js image pushed to ECR with a health endpoint.
- 02
ECS service
Fargate task definition, service and two target groups.
- 03
CodeDeploy
AppSpec file, deployment group and traffic-shift settings.
- 04
Validation
Lifecycle hook Lambda that smoke-tests the green tasks.
- 05
Rollback
Alarm-driven rollback shown against a deliberately broken build.
After this, you will be able to
- Explain blue-green against rolling and canary releases
- Defend the checks that must pass before traffic moves
- Demo a bad release being rolled back without manual steps
Technology stack
- AWS ECS
- AWS Fargate
- AWS CodeDeploy
- Application Load Balancer
- Docker
- Node.js
- Level
- Major Project
- Domain
- Cloud & DevOps
- Build time
- 3-4 weeks
- Difficulty
You receive
- Complete, commented source code
- 60-90 page project report (IEEE format)
- Editable presentation deck
- Architecture, ER and UML diagrams
- Local setup and deployment guide
- Sample dataset or seed data
- Viva question bank with answers
- One 45-minute walkthrough call
- 30 days of doubt-clearing support