Source
GitHub → CodePipeline
Notices your push and takes a snapshot of the code.
- Your commit reaches GitHub
- GitHub tells AWS
- A copy of the code is saved
Produces SourceArtifact
CI/CD is the automation that carries a code change to real users: it builds it, tests it, deploys it and checks it works. Make a change, push it, and watch it happen.
You are a developer on the ShortLink team. Pick what you are about to push.
Expected: everything passes and production gets the new version.
Real pipelines also fail for boring reasons: a missing permission, a stopped agent. Switch one on, then push.
Each box is a stage in AWS CodePipeline. Nothing here is clicked by a person.
GitHub → CodePipeline
Notices your push and takes a snapshot of the code.
Produces SourceArtifact
AWS CodeBuild
Builds the code and runs the tests on a clean machine.
Produces BuildArtifact.zip
AWS CodeDeploy → EC2
Installs the tested package on the server, then checks it is healthy.
Uses BuildArtifact.zip
EC2 behind a load balancer
What your users actually reach.
a1b2c3dserved error (503)
Waiting for traffic…
The same run, drawn as the AWS services involved. Click any box to see what it is.
How to read this
A box lights up while it is doing work.
A label travelling along a line is data moving between services.
Click any box to see what it is and where to find it in the AWS console.
Status