CI/CD on AWS with the Developer Tools
Build a complete CI/CD pipeline on AWS with the Developer Tools suite: CodeCommit, CodeBuild, CodeArtifact, CodeDeploy and CodePipeline. The series goes from the concepts to a real pipeline that takes code from CodeCommit through build and test, then a blue/green deploy onto an EC2 Auto Scaling Group with a manual approval gate and automatic rollback. All infrastructure is built with the AWS CLI, every command is run for real on AWS, and the code lives at github.com/nghiadaulau/aws-cicd-series. Grounded in the official AWS docs.
A Pragmatic Pipeline: Approval Gate, Parallelism, and Triggers
A pipeline that runs isn't yet a pipeline you can use at work. This article adds three pragmatic things: a manual approval gate that blocks deploy until someone signs off (demoed for real over the CLI), running multiple actions in parallel with runOrder, and trigger filtering so the pipeline runs only for the right branch — using pipeline type V2.
Quality and Notifications in the Pipeline
A pipeline needs two more things to use for real: running test/scan as a blocking gate (broken code never reaches Deploy) and firing status notifications so nobody has to sit watching the console. This article uses tests in the Build stage as a gate, then sets up a notification rule that pushes pipeline events to SNS — reading a real notification through SQS to prove the chain works.
Capstone (1): Building the Target Infrastructure via CLI
Opening the capstone: assembling every piece of infrastructure we've learned into a production target environment for a complete pipeline. A launch template and Auto Scaling Group behind an Application Load Balancer, a blue/green deployment group with rollback — all via the AWS CLI. The next article wires up a pipeline that runs straight into this infrastructure.
Capstone (2): The Complete Production Pipeline
Closing the series: a pipeline that carries code from a CodeCommit commit, through build and test, through an approval gate, then blue/green deploys onto an Auto Scaling Group behind an ALB — running for real end-to-end, one commit becoming one zero-downtime production release. Then tearing everything down and wrapping up the whole series with a roadmap for what's next.