A SysOps Administrator is tasked with setting up automated patch management for a fleet of Amazon Linux 2 EC2 instances. The organization requires that a custom patch baseline be applied to these instances during a specific weekly maintenance window. The patching process must target only the instances configured with the patch group 'Prod-Linux'. Arrange the following steps in the correct chronological sequence to configure this automated workflow.
- 1Create a custom patch baseline with the required approval rules for Amazon Linux 2.
- 2Tag the target EC2 instances using the case-sensitive key 'Patch Group' and value 'Prod-Linux'.
- 3Associate the 'Prod-Linux' patch group with the newly created custom patch baseline.
- 4Create a Maintenance Window and register the target instances using the 'Patch Group' tag.
- 5Register a Task in the Maintenance Window to execute the 'AWS-RunPatchBaseline' SSM document.
Answer
The correct sequence starts with creating the custom patch baseline, followed by tagging the instances with the case-sensitive 'Patch Group' tag, associating that patch group with the baseline, creating the Maintenance Window with registered targets, and registering the Run Command task to execute the AWS-RunPatchBaseline document.
The correct sequence begins with creating the custom patch baseline first to define approval rules. Next, target EC2 instances are tagged with the case-sensitive 'Patch Group' tag. The patch group is then registered with the custom baseline so Patch Manager maps the instances to this baseline instead of the default. After that, a Maintenance Window is defined, and the instances are registered as targets using their patch group tags. Finally, the task is registered in the Maintenance Window to run the 'AWS-RunPatchBaseline' SSM document on the registered targets.
Step-by-Step Solution
Key Concept
Automated operating system patching using Systems Manager Patch Manager, custom baselines, patch groups, and maintenance windows.
Estimated Time:2m 0s