Hands-on emulator lab · 6–10 min
Write a patch approval baseline — Systems Manager and Patch Manager
Create a patch approval baseline and inspect its saved rule.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Create a patch approval baseline and inspect its saved rule.
Why this matters
Server updates need an intentional approval policy. You will choose a delay for security patches and inspect the saved baseline. This lab does not assign machines or install updates.
Words you will use
A patch fixes or updates software. A baseline defines approved patches. An approval delay waits a chosen time before an update becomes eligible.
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 a patch approval delay
Create an Amazon Linux 2 baseline that approves security patches after your chosen delay. A delay gives teams time to test updates; it is not a promise that every patch is safe. No managed machines are assigned to this baseline.
Days before approval: Choose 0–30 days. Zero means no approval delay in this rule. Suggested practice value: 7.
2. Inspect the saved approval rule
Read the baseline by its returned ID. Compare the operating system, security filter, and approval delay with your setup. The emulator does not implement patch-group registration. This lab verifies a stored policy, not installed updates or a patched server.
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.