Keep app secrets out of code — Secrets Manager

Your goal

Create a practice secret, replace its value, and retrieve the latest version.

Why this matters

Apps can retrieve a value by secret ID instead of copying it into source code. You will save, replace, and retrieve harmless practice text. No real password or access key belongs in this lab.

Words you will use

A secret is sensitive data such as a database password. Rotation replaces a secret. A role gives an app permission to retrieve it.

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 fake secret

Create a secret containing the harmless text practice-start. Do not enter a real password or API key. The purpose is to learn how apps retrieve a value by ID instead of copying it into source code.

2. Save a new practice value

Enter an invented message and save it as a new secret version. The request returns version information. This change does not rotate a real database password.

Practice message: Type a short message that you can recognize in the API result. Suggested practice value: Hello from my lab.

3. Retrieve the current value

Read the secret’s current version and compare it with your message. The response contains practice data, so it is safe to inspect here; production secret values should not be logged.

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.