Course contentsShow
← Cloud and Infrastructure
Lesson 1838 of 2,98938. AWS Native CI/CDFree lesson

CodePipeline Architecture and Components

Understanding CodePipeline stages, actions, transitions, and how they orchestrate the CI/CD workflow.

CodePipeline Architecture and Components

What you'll learn: How CodePipeline's building blocks—stages, actions, and transitions—work together to orchestrate your entire CI/CD workflow.

The Orchestra of CI/CD

Think of CodePipeline as a conductor coordinating different musicians (AWS services) to perform a symphony (your software delivery). Each section of the orchestra plays in sequence, and the conductor ensures smooth handoffs between them.

Stages: The Major Sections

A stage represents a logical phase in your pipeline, like "Source," "Build," "Test," or "Deploy." Stages execute sequentially by default—one must complete before the next begins. Each stage groups related work together.

Source → Build → Test → Deploy

Actions: The Individual Performers

Within each stage, actions are the actual work units. An action might pull code from CodeCommit, trigger a CodeBuild project, or invoke CodeDeploy. Actions within a stage can run sequentially or in parallel, depending on your configuration.

For example, your "Test" stage might run unit tests and integration tests simultaneously as parallel actions.

Transitions: The Handoffs

Transitions are the connections between stages. They control the flow of artifacts and execution. You can disable transitions to pause the pipeline or enable manual approval actions that require human intervention before proceeding.

Artifacts: The Sheet Music

As your pipeline progresses, artifacts (like compiled code or build outputs) flow between stages. These are stored in S3 and passed along, so each stage has access to what previous stages produced.

The Complete Picture

CodePipeline orchestrates these components: stages provide structure, actions perform work, transitions manage flow, and artifacts carry data forward—creating an automated pathway from commit to production.

Key Takeaway: CodePipeline architecture uses stages (phases), actions (work units), and transitions (flow control) to orchestrate your CI/CD workflow, with artifacts flowing through each step.