Give each release a clear path to production — CodePipeline and CodeBuild

Your goal

Plan a release pipeline with visible checks and a deliberate production step.

Why this matters

A team deploys changes by copying commands between chat messages. You will arrange repeatable stages, pass the same tested output forward, and decide when a person should review the release.

Words you will use

A pipeline connects release stages. A stage groups actions such as build or deploy. An artifact carries output between actions. An approval pauses progress for a human decision.

How to proceed

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

1. Put the work in order

A code change should be built and checked before it reaches production. The team needs a repeatable path with visible status.

What should the pipeline define?

Ordered source, build/test, and deployment actions.

CodePipeline coordinates release actions and their results. Services such as CodeBuild perform particular work. Define which checks must pass and how failures stop the release from moving forward.

The release has a visible sequence of required steps.

Source → build and checks → deployment

2. Deploy what passed the checks

The test stage checks one artifact, but the deployment stage rebuilds from a moving branch. It might deploy different code.

What should move between stages?

The same identified artifact from the successful build.

Tie the release to a source revision and pass the tested artifact forward. Rebuilding from changing inputs can break that link. Traceability helps the team know exactly what was approved and deployed.

The production candidate matches the tested release.

Tested artifact identity → next stage → same release

3. Make approval meaningful

This production change needs a human review. An approver should understand what changed and how to recover if the release has a problem.

What should accompany approval?

Change details, check results, impact, and rollback information.

Use approval where the workflow requires it and provide evidence for a real decision. Approval complements automated checks; it does not replace them. Record the result and keep deployment permissions appropriately scoped.

The release decision has useful evidence and recovery context.

Checks + change context + recovery plan → informed approval

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.