1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
This seems to be a limitation with the document "AWSEC2-PatchLoadBalancerInstance". A possible workaround for this would be to clone the document and provide an assume role manually within the automation document itself. Please follow below steps for the same -
- Go to AWS Systems Manager service --> Documents
- Search and select the document "AWSEC2-PatchLoadBalancerInstance"
- Click on Actions --> Clone document
- Under the field 'Assume Role - optional', provide the ARN of the Role 'AWSServiceRoleForAmazonSSM' and click on Create Automation at the bottom of the screen
- Use this cloned copy to create SSM association
Alternatively, you can use AWS Maintenance Windows to patch your LB instances using the document 'AWSEC2-PatchLoadBalancerInstance'.
Hope this helps!
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago