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

Creating a Basic Pipeline

Building a simple CodePipeline with source, build, and deploy stages using the AWS Console.

Creating a Basic Pipeline

You'll learn how to build your first CodePipeline through the AWS Console, connecting source, build, and deploy stages into a working automation workflow.

What Is a Basic Pipeline?

Think of CodePipeline as an assembly line for your code. Just as a factory product moves through stations—raw materials → assembly → quality check → packaging—your code moves through stages: pulling from source control → building/testing → deploying to servers. Creating a basic pipeline means connecting these three fundamental stages into one automated flow.

The Three Essential Stages

In the AWS Console, you'll configure:

  1. Source Stage: Where your code lives (CodeCommit, GitHub, or S3). When code changes, the pipeline automatically triggers.

  2. Build Stage: Uses CodeBuild to compile code, run tests, and package artifacts. You reference your buildspec file here.

  3. Deploy Stage: Uses CodeDeploy (or direct ECS/Lambda integration) to push your built artifact to target environments.

Console Creation Flow

When you create a pipeline in the AWS Console, you'll:

  • Name your pipeline and choose or create a service role
  • Select your source provider and repository
  • Configure build provider (CodeBuild project)
  • Configure deploy provider (CodeDeploy application or direct deployment)
  • Review and create

CodePipeline automatically creates an S3 bucket to store artifacts between stages. Each stage passes its output as input to the next stage—your source code flows to the builder, and built artifacts flow to deployment.

Why This Matters

Once created, your pipeline runs automatically whenever code changes. No manual coordination between services—CodePipeline orchestrates everything, tracking progress and showing which stage succeeded or failed.

Key Takeaway: A basic CodePipeline connects source → build → deploy stages through the AWS Console, automating the entire journey from code commit to production deployment with visual monitoring and automatic artifact passing between stages.