Build the same setup from a written plan — CloudFormation

Your goal

Plan a repeatable cloud setup using a template you can review.

Why this matters

A teammate needs the same infrastructure in a test environment. You will describe it as code, review a proposed change, and protect important data when resources change.

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

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

1. Write the desired setup

A manual checklist keeps producing slightly different environments. The team wants a versioned description of the resources and their settings.

What should define the setup?

A CloudFormation template kept under version control.

A template describes the intended resources, relationships, and configurable values. Version control lets the team review changes and understand history. Test the template; a written plan can still contain mistakes.

The environment has a repeatable, reviewable definition.

Versioned template + environment values → stack

2. Review before applying

A template update may replace a resource rather than edit it in place. The team needs to inspect the proposed work before execution.

What should they review?

A change set and the affected resources’ update behavior.

A change set helps preview proposed additions, modifications, and removals. Check replacement and dependency impacts. It is a planning aid, not a guarantee that every operation will succeed without interruption.

The team understands the proposed infrastructure changes.

Updated template → change set → review → execute

3. Protect valuable data

A database or bucket contains data that must survive a planned resource change. A failed update could also require recovery.

What must the plan include?

Suitable retention policies, backups, and a tested recovery plan.

Review deletion and replacement policies for stateful resources and protect the underlying data. Test recovery and understand rollback limits. Infrastructure automation does not remove responsibility for data lifecycle decisions.

The change includes a deliberate data protection plan.

Resource change + retention/backup plan → recoverable update

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.