usheru Track- Tracking System Deployment

Overview

• Production → uts.usheru.com

• Development → uts-dev.usheru.com

Workflow Summary

1. Source Control (GitHub)

   • Repository: usheru-tracking

   • Branches:

     • main → triggers production pipeline deployment

     • test → triggers development pipeline deployment

2. CI/CD Pipeline (AWS CodePipeline)

   • Orchestrates the build and deployment process.

   • Stages:

     • Source Stage

       • Retrieves source code from GitHub.

       • Stores artifacts in an S3 bucket (codepipeline-eu-west-1/SourceArtifact).

     • Build Stage

       • Builds and tests a Docker image.

       • Stores build artifacts in S3 (codepipeline-eu-west-1/BuildArtifact).

       • Pushes Docker image to ECR (Elastic Container Registry) (usheru-tracking ECR repo).

     • Deploy Stage

       • Creates a new ECS task definition.

       • Deploys new ECS service version.

3. ECS (Elastic Container Service)

   • Runs Docker containers on an EC2-backed ECS cluster.

   • New tasks are registered and deployed during each pipeline execution.

4. Networking & Load Balancing

   • Application Load Balancer (ALB):

     • Registered with ECS target group (EC2 instances).

     • Routes traffic to ECS containers via private IPs.

   • Route 53:

     • Routes external requests to ALB via CNAME records.

     • Endpoints:

       • Production → uts.usheru.com

       • Development → uts-dev.usheru.com

Deployment Flow

1. Developer commits code to main or test branch in GitHub.

2. AWS CodePipeline is triggered.

3. Pipeline retrieves source and stores it in S3.

4. CodeBuild:

   • Builds and tests Docker image.

   • Pushes new image to ECR.

   • Stores build artifacts.

5. ECS deploys a new task definition using the updated image.

6. ECS service runs containers in EC2 cluster.

7. Application Load Balancer routes traffic to updated ECS containers.

8. Route 53 resolves domain names to the ALB.

Key AWS Services Used

• GitHub → Source code repository

• AWS CodePipeline → CI/CD orchestration

• Amazon S3 → Artifact storage (source + build)

• AWS CodeBuild → Build and test Docker images

• Amazon ECR → Container image repository

• Amazon ECS (with EC2 launch type) → Container orchestration

• Application Load Balancer (ALB) → Traffic distribution across ECS containers

• Amazon Route 53 → DNS routing to application endpoints

Endpoints

Notes

• Separate pipelines for prod and dev ensure isolation between environments.

• New ECS task definitions ensure that rollbacks can be performed if needed.

• The ALB provides high availability and fault tolerance.

• ECS runs containers on an EC2 target group with auto-scaling capabilities (if configured).