Keep a shop’s data together — RDS

Your goal

Create a database instance record and set its backup retention period.

Why this matters

A database backup policy needs an intentional retention period. You will create a database configuration, choose how many days it keeps backup history, and verify that setting. The emulator does not run PostgreSQL here.

Words you will use

A relational database stores linked tables. A join combines related rows. A transaction keeps a group of changes together.

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 practice database

Create a PostgreSQL instance configuration with a fixed practice password kept on the server. The emulator models the API resource; this does not start a PostgreSQL server you can connect to.

2. Set backup retention

Choose how many days of automated backup history the database should retain, then save the setting. The lab checks configuration rather than waiting days for scheduled backups.

Backup retention days: Choose 1–35 days of backup retention. Suggested practice value: 7.

3. Inspect the database settings

Describe the database and find BackupRetentionPeriod in the response. Compare it with your chosen number and note that an API configuration is different from a tested restore.

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.