Hands-on emulator lab · 6–10 min
Build and test an app the same way each time — CodeBuild
Create a build project and give it a bounded timeout.
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 build project and give it a bounded timeout.
Why this matters
Repeatable builds need a defined environment and a sensible timeout. You will create a project with fixed harmless instructions and change its time limit. The project is not executed in this lab.
Words you will use
A build turns source files into usable output. A buildspec describes build commands and outputs. An artifact is the result saved for another step, such as a deployment.
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 practice build project
Create a project with a fixed build instruction that only prints a practice message. The source type is NO_SOURCE and artifacts are disabled. This lab stores a build definition; it does not execute a build container.
2. Choose a time limit
Set how many minutes a build may run before timing out. A useful limit allows normal work while catching jobs that stall. This setting is saved without starting a job.
Build timeout in minutes: Choose 5–60 minutes for the practice project. Suggested practice value: 15.
3. Inspect the project definition
Get the project and compare timeoutInMinutes with your choice. You can also inspect the fixed build specification in the response. No source code from visitors is executed.
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.