GitLab-Jenkins-ECS CI/CD Pipeline

aws · architecture diagram.

Diagrams.so

About This Architecture

GitLab-triggered Jenkins pipeline builds containerized microservices and pushes images to AWS ECR, enabling automated deployment across multi-AZ ECS Fargate clusters. Jenkins EC2 t3.medium instances orchestrate the CI stage, while CodeDeploy executes blue-green deployments to redundant ECS clusters spanning ap-northeast-2a and ap-northeast-2b availability zones. Application Load Balancers distribute traffic across TAS, BAT, and ADM services with automatic failover between primary and standby ALBs, ensuring high availability and zero-downtime deployments. Fork this diagram to customize VPC CIDR blocks, service names, or add additional deployment stages like staging or canary releases. The architecture demonstrates enterprise-grade CI/CD with infrastructure-as-code readiness and multi-region failover patterns.

People also ask

How do I set up a multi-AZ CI/CD pipeline with GitLab, Jenkins, and ECS Fargate on AWS with blue-green deployments?

This diagram shows a production-grade CI/CD architecture where GitLab webhooks trigger Jenkins builds on EC2 t3.medium, which push container images to ECR and invoke CodeDeploy for blue-green deployments across redundant ECS Fargate clusters in two availability zones. Application Load Balancers distribute traffic with automatic failover, ensuring zero-downtime updates and high availability for mic

GitLab-Jenkins-ECS CI/CD Pipeline

AWSadvancedCI/CDECS FargateJenkinsGitLabCodeDeploy
Domain: Devops CicdAudience: DevOps engineers implementing multi-AZ CI/CD pipelines with GitLab, Jenkins, and ECS Fargate
0 views0 favoritesPublic

Created by

March 9, 2026

Updated

March 9, 2026 at 5:05 AM

Type

architecture

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI