Patch Manager
- Go to the AWS Management Console
- Find Systems Manager
- Select Systems Manager
![Patch Manager](/images/3-PatchManager/0001-patchmanager.png)
- In the AWS Systems Manager interface
![Patch Manager](/images/3-PatchManager/0002-patchmanager.png)
- In the Fleet Manager interface. We wait about 10 minutes from assigning IAM Role to Windows instance
- Select Managed nodes
- We have 2 nodes, Windows-Lab-SSM-1 and Windows-Lab-SSM-2
![Patch Manager](/images/3-PatchManager/0003-patchmanager.png)
- In the Fleet Manager interface
- Select node Windows-Lab-SSM-1
- Select Node actions
- Select Start terminal session
![Patch Manager](/images/3-PatchManager/0004-patchmanager.png)
- Session is initialized
![Patch Manager](/images/3-PatchManager/0005-patchmanager.png)
- Same for the Windows-Lab-SSM-2 node
- Select Windows-Lab-SSM-2
- Select Node actions
- Select Start terminal session
![Patch Manager](/images/3-PatchManager/0006-patchmanager.png)
- Check the connection of 2 Windows EC2 Instances successfully
![Patch Manager](/images/3-PatchManager/0007-patchmanager.png)
- In the Fleet Manager interface
![Patch Manager](/images/3-PatchManager/0008-patchmanager.png)
- In the Patch Manager interface
![Patch Manager](/images/3-PatchManager/0009-patchmanager.png)
- In the Basic configuration interface
- Patch operation, select Scan and install
- Reboot option, select Do not reboot my instance
- Instance to path, select Patch only the target instances specify
- Select Choose instances manually
- Select 2 Windows EC2 Instances
![Patch Manager](/images/3-PatchManager/00010-patchmanager.png)
- Select Patch now
![Patch Manager](/images/3-PatchManager/00011-patchmanager.png)
- Wait about 1 minute then refresh to see the successful patch result
![Patch Manager](/images/3-PatchManager/00012-patchmanager.png)