You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In the SSM Quick Setup Patching Patching guide, the post-deployment checks instruct you to create an EC2 instance and Ensure that the EC2-Default-SSM-AD-Role is selected as the IAM Profile.
Does this mean that SSM QS Patching in ASEA will only work with the EC2-Default-SSM-AD-Role?
What if customers want to use a custom IAM profile on their EC2 instances? Will they have to add the required policies and tags manually to this role?
The text was updated successfully, but these errors were encountered:
Bug reports which fail to provide the required information will be closed without action.
Required Basic Info
Describe the bug
In the SSM Quick Setup Patching Patching guide, the post-deployment checks instruct you to create an EC2 instance and
Ensure that the EC2-Default-SSM-AD-Role is selected as the IAM Profile
.Does this mean that SSM QS Patching in ASEA will only work with the EC2-Default-SSM-AD-Role?
What if customers want to use a custom IAM profile on their EC2 instances? Will they have to add the required policies and tags manually to this role?
The text was updated successfully, but these errors were encountered: