Build the same setup from a written plan — CloudFormation

Your goal

Create a stack from a template, then update its bucket configuration.

Why this matters

A written infrastructure plan can be updated as one stack. You will submit a template, change its versioning property, and inspect the new stored version after the update completes.

Words you will use

A template describes resources and settings. A stack manages resources from a template. A change set previews proposed changes. Replacement creates a new resource in place of an old one.

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 the first stack version

Send a small JSON template describing one S3 bucket to CloudFormation. A stack groups resources described by a template. Wait for its create operation to finish before changing it.

2. Update the written plan

Submit a new version of the same template with bucket versioning enabled. This is an update to the same stack, not a separate manual bucket edit. The operation can have its own status and errors.

3. Inspect the current stack template

Read the stack’s current template and verify the versioning property. This lab checks stack lifecycle and template state. It does not assume that the emulator implements every resource provider or production rollback behavior.

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.