Compare the running setup with its template — CloudFormation and Drift detection

Your goal

Request a stack drift check and inspect the detection result.

Why this matters

Changes outside a template can make infrastructure differ from its written plan. You will request drift detection and inspect its report. Coverage depends on the emulator’s supported resource properties.

Words you will use

Drift is a difference between expected and actual settings. A stack groups resources. Unsupported resources or properties may not be checked.

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 small template stack

Create a stack from a one-bucket template and wait for completion. Drift compares supported resource properties with the template’s expected values. It is not a check of every possible setting.

2. Request drift detection

Ask CloudFormation to detect drift on this stack and save the returned detection ID. This starts an operation separate from creating or updating the stack.

3. Inspect the detection report

Read the report using its detection ID. Check completion and the reported drift status. This lab exercises the emulator’s detection API; it does not prove full provider coverage or automatically repair changes.

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.