About This Architecture

AWS CodePipeline orchestrates a four-stage CI/CD workflow—source, build, test, and deploy—using CodeCommit, CodeBuild, and CodeDeploy within a single availability zone. Developers push code to CodeCommit, triggering CodePipeline to build artifacts cached in S3, run tests via CodeBuild, and await manual approval before deploying to EC2 instances in a public subnet. The architecture isolates application servers and RDS databases in separate subnets, with CloudWatch monitoring and SNS notifications for pipeline events. Fork this diagram on Diagrams.so to customize stages, add multi-AZ resilience, or integrate additional AWS services like Lambda or CodeStar. Single-AZ deployment is suitable for non-production environments; production workloads should extend this pattern across multiple availability zones for high availability.

People also ask

How do I set up a CI/CD pipeline on AWS using CodePipeline and CodeBuild with approval gates and EC2 deployment?

This diagram shows a complete four-stage AWS CI/CD pipeline: CodeCommit triggers CodePipeline, CodeBuild compiles and tests code with S3 caching, an approval gate gates manual review, and CodeDeploy pushes to EC2 instances. The architecture includes RDS and ElastiCache for application dependencies, CloudWatch for monitoring, and SNS for notifications—all within a single availability zone.