portfolio

🎡 Blue-Green Deployment System

AWS Docker ECS CodePipeline

Zero-downtime deployment pipeline ensuring 99.9% availability for mission-critical applications

📋 Problem Statement

Traditional deployment strategies face critical challenges:

💡 Solution: Automated Blue-Green Deployment

A fully automated deployment pipeline that maintains two identical production environments (Blue and Green), enabling instant traffic switching and zero-downtime releases.

Key Features

🏗️ Architecture

```mermaid graph TB A[GitHub Repository] –>|Code Push| B[CodePipeline] B –>|Build| C[CodeBuild] C –>|Docker Image| D[ECR] D –>|Deploy| E[CodeDeploy] E –>|Update| F[ECS Green Environment] F –>|Health Check| G{Smoke Tests Pass?} G –>|Yes| H[ALB Traffic Switch] G –>|No| I[Rollback] H –>|Route Traffic| J[Users] K[ECS Blue Environment] -.->|Standby| H

style E fill:#FF9900
style F fill:#00FF00
style K fill:#0000FF
style H fill:#FF6B6B \`\`\`

Deployment Flow

  1. Code Commit: Developer pushes code to GitHub
  2. Build Phase: CodeBuild creates Docker image and pushes to ECR
  3. Deploy to Green: CodeDeploy updates Green environment with new version
  4. Smoke Tests: Automated tests validate Green environment
  5. Traffic Switch: ALB routes traffic from Blue to Green
  6. Blue Standby: Old Blue environment kept for quick rollback

📁 Project Structure

``` blue-green-deployment/ ├── buildspec.yml # CodeBuild configuration ├── scripts/ │ └── smoke_tests.sh # Automated validation tests └── task_definitions/ ├── blue_task_def.json # ECS Blue task definition └── green_task_def.json # ECS Green task definition ```

🚀 Setup & Deployment

Prerequisites

Installation Steps

  1. Clone the repository ```bash git clone https://github.com/Abhinandansinha01/portfolio.git cd blue-green-deployment ```

  2. Create ECS Cluster ```bash aws ecs create-cluster –cluster-name production-cluster ```

  3. Set up Application Load Balancer ```bash

    Create ALB with two target groups (Blue and Green)

    aws elbv2 create-load-balancer –name app-alb
    –subnets subnet-12345 subnet-67890
    –security-groups sg-12345 ```

  4. Configure CodePipeline
    • Source: GitHub repository
    • Build: CodeBuild with buildspec.yml
    • Deploy: CodeDeploy with Blue/Green configuration

  5. Deploy initial version ```bash

    Pipeline will automatically trigger on code push

    git push origin main ```

⚙️ Configuration

buildspec.yml

The build specification defines the CI/CD process:

```yaml version: 0.2 phases: pre_build: commands: - echo Logging in to Amazon ECR… - aws ecr get-login-password | docker login –username AWS –password-stdin $ECR_URI build: commands: - echo Building Docker image… - docker build -t $IMAGE_REPO_NAME:$IMAGE_TAG . - docker tag $IMAGE_REPO_NAME:$IMAGE_TAG $ECR_URI/$IMAGE_REPO_NAME:$IMAGE_TAG post_build: commands: - echo Pushing Docker image… - docker push $ECR_URI/$IMAGE_REPO_NAME:$IMAGE_TAG ```

Smoke Tests

Automated validation before traffic switch:

```bash

!/bin/bash

Test health endpoint

curl -f http://green-env.internal/health   exit 1

Test critical API endpoints

curl -f http://green-env.internal/api/status   exit 1

Performance check

response_time=$(curl -o /dev/null -s -w ‘%{time_total}’ http://green-env.internal/) if (( $(echo “$response_time > 2.0” | bc -l) )); then echo “Response time too slow: $response_time” exit 1 fi ```

📊 Deployment Metrics

Metric Before Blue-Green After Blue-Green Improvement
Deployment Downtime 15-30 minutes 0 seconds 100%
Rollback Time 30-60 minutes < 1 minute 98%
Failed Deployments 5% 0.1% 98%
Availability 99.5% 99.9% 0.4% increase

Real-World Impact

🔄 Deployment Strategies

Standard Blue-Green

Canary Deployment (Advanced)

  1. Route 10% traffic to Green
  2. Monitor metrics for 10 minutes
  3. Gradually increase to 50%, then 100%
  4. Rollback if errors detected

Traffic Splitting Configuration

```json { “targetGroups”: [ { “name”: “blue-tg”, “weight”: 100 }, { “name”: “green-tg”, “weight”: 0 } ] } ```

🛡️ Rollback Strategy

Automatic Rollback Triggers

Rollback Process

```bash

Instant rollback by switching ALB target group

aws elbv2 modify-listener –listener-arn $LISTENER_ARN
–default-actions Type=forward,TargetGroupArn=$BLUE_TG_ARN ```

📈 Monitoring & Alerts

CloudWatch Metrics

Alarms

🔧 Troubleshooting

Common Issues

Issue: Smoke tests failing

Issue: Traffic not switching

Issue: Container fails to start

🔄 Future Enhancements

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

📄 License

This project is open source and available under the MIT License.

👤 Author

Abhinandan Sinha

Deploying with confidence, zero downtime at a time 🚀
This site is open source. Improve this page.