About This Architecture

Cumberland Hotels' serverless CI/CD pipeline orchestrates code from GitHub through GitHub Actions and Jenkins, building Docker images, scanning for security vulnerabilities, and deploying to ECS Fargate and Lambda across dev, QA, UAT, and production environments. AWS CodePipeline coordinates the entire workflow, pulling artifacts from ECR and S3 while enforcing approval gates and cross-account IAM roles for environment isolation. Unit tests, SAST security scans, and code quality gates run automatically before deployment, with test reports stored in S3 for audit trails. The architecture demonstrates enterprise-grade CI/CD with blue-green deployments in production, rollback capabilities, and centralized observability through CloudWatch, CloudTrail, X-Ray, and Security Hub. Fork this diagram on Diagrams.so to customize branch strategies, add additional environments, or adapt the approval gate logic for your organization. This pattern is ideal for teams managing multiple deployment targets and requiring strict separation of concerns across development, testing, and production accounts.

People also ask

How do you build a multi-environment CI/CD pipeline on AWS that deploys to both ECS Fargate and Lambda with automated security scanning and approval gates?

This diagram shows a complete serverless CI/CD architecture where GitHub Actions triggers Jenkins builds, which create Docker images pushed to ECR. AWS CodePipeline orchestrates deployments across dev, QA, UAT, and production environments using CodeDeploy with blue-green deployments, while cross-account IAM roles enforce environment isolation and approval gates control production releases.