What is CI/CD?

🏭

SDLC Automation on AWS

Every code change flows through the same automated path — CodePipeline orchestrates, CodeBuild tests, CodeDeploy ships. No manual steps, no surprises.

~77 min total12 modules9 quiz questionsDOP-C02 High priority

CI/CD — Continuous Integration / Continuous Delivery — is the practice of automatically building, testing, and deploying every code change. The goal: eliminate the "works on my machine" problem and make production deployments boring and routine.

Click each stage to learn what happens

→→→

CI vs CD — What's the Difference?

Continuous Integration

Every commit is automatically built and tested. Catches integration bugs early, prevents long merge conflicts.

Continuous Delivery

Tested artifacts are automatically prepared for release. A human still clicks "deploy to prod."

CD++

Continuous Deployment

Every passing build goes straight to production with no human gate. Requires high test confidence.

The AWS Toolchain

AWS provides a complete managed CI/CD suite. CodePipeline is the orchestrator (the conveyor belt). CodeBuild compiles and tests inside ephemeral containers. CodeDeploy ships artifacts to EC2, Lambda, or ECS. CodeArtifactstores and proxies package dependencies.

💡Factory analogy: CodePipeline = conveyor belt · CodeBuild = machine shop · CodeDeploy = delivery crew · S3 = pallets carrying artifacts between stations. If any station fails, the belt stops — nothing downstream runs.