Instiq
Chapter 4 · Deployment·v2.1.0·Updated 6/28/2026·~9 min

What's changed: In-scope service coverage (axis B): added CodeArtifact/CloudShell (s1) and Amplify (s3) definitions, roles, and selection criteria.

4.1CI/CD Pipelines

Key points

Understand CI/CD basics: automating source→build→test→deploy with CodePipeline, the roles of CodeBuild (build/test) and CodeDeploy (deploy), and buildspec. The core of "Deployment" in DVA-C02.

CI/CD automatically builds, tests, and deploys code changes. On AWS, CodePipeline orchestrates the whole flow, with dedicated services for each stage.

4.1.1Pipeline stages

Diagram showing stages Source (CodeCommit/Git) → Build (CodeBuild) → Test (CodeBuild) → Deploy (CodeDeploy) orchestrated by CodePipeline, where a commit triggers build → test → deploy.
CI/CD with CodePipeline
  • CodePipeline: orchestrates the whole flow source→build→test→deploy.
  • CodeBuild: builds/tests the source; steps are defined in buildspec.yml.
  • CodeDeploy: deploys to EC2/on-prem/Lambda/ECS; steps in appspec.
  • CodeCommit is a Git repo (external Git works too); a commit triggers the pipeline. Note: CodeCommit is closed to new customers since July 2024 (existing use continues); new setups typically use GitHub etc. with CodeConnections.
Exam point

Common on DVA: orchestration = CodePipeline, build/test steps = CodeBuild’s buildspec.yml, deploy steps = CodeDeploy’s appspec. Watch for swapped roles.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.

Get started freeLog in