Create a check that follows a visitor’s path — CloudWatch Synthetics

Your goal

Create a canary configuration and inspect how long it keeps successful results.

Why this matters

A scripted availability check needs a definition and a place for its results. You will create an unstarted canary configuration and choose result retention. No browser check or uptime measurement is run.

Words you will use

A canary is a scripted check. A schedule controls when it runs. Artifacts are outputs such as logs or screenshots from a real run.

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. Prepare result storage and a role

Create an S3 bucket for canary artifacts and a Lambda service role. A canary is a small scripted check. This exercise will store its configuration without starting a browser or contacting a website.

2. Save the practice canary

Choose a retention period and create a canary with a fixed, harmless handler. The canary stays unstarted. Its schedule and result location are configuration records in the emulator.

Days to keep successful results: Choose 1–30 days. No canary run is started in this lab. Suggested practice value: 7.

3. Inspect the canary settings

Get the canary and compare its retention period, schedule, and artifact location. This does not claim that a page was tested or an availability measurement was collected.

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.