Hands-on emulator lab · 6–10 min
Give each release a clear path to production — CodePipeline and CodeBuild
Create a two-stage release pipeline and pause its review-stage entry.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Create a two-stage release pipeline and pause its review-stage entry.
Why this matters
A release path needs clear stages and controls for moving between them. You will create a source-and-review pipeline, pause entry to review, and inspect the transition state. No release is deployed.
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
Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.
1. Create a source and review pipeline
Create an artifact bucket, a service role, and a pipeline with an S3 source followed by manual approval. This records a release path. It does not upload source or start a deployment.
2. Pause entry to review
Disable the inbound transition to the Review stage and record a practice reason. This is a pipeline control, separate from approving a particular execution.
3. Inspect the transition state
Read the pipeline state and find the disabled inbound transition. This lab verifies the pause setting, not a completed build, approval, or production release.
Practice, then check your understanding
Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.
Read the official AWS documentation for service behavior and production details.