Set safe admin-session preferences — Systems Manager and Session preferences

Your goal

Create a Session Manager preferences document with an idle timeout.

Why this matters

Admin sessions need clear preferences, including when an idle session should end. You will save and read a Session Manager document. The emulator does not open an interactive shell in this lab.

Words you will use

Session Manager can provide controlled admin access to managed machines. A Session document stores preferences. An idle timeout is how long a quiet session may remain open. This lab does not open a shell.

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. Choose an idle timeout

Enter how many quiet minutes should end a practice admin session, then save a Session document. An idle limit reduces the chance of leaving an unattended session open.

Idle timeout in minutes: Choose 1–60 minutes. This document does not open a terminal. Suggested practice value: 20.

2. Label the preferences document

Add a Purpose tag to identify this configuration. Session Manager also needs managed-node setup, permissions, and network access. A preferences document is only one piece.

3. Read the preferences back

Retrieve the JSON document and compare idleSessionTimeout with your choice. This lab verifies configuration. The emulator does not open an interactive shell for this exercise.

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.