A SysOps Administrator is setting up an AWS Systems Manager Automation execution that uses a custom runbook to perform administrative tasks across multiple Amazon EC2 instances. The SSM Agent is running on all target instances, and an IAM instance profile containing the AmazonSSMManagedInstanceCore policy is already attached. When the administrator attempts to start the Automation execution using a service role, the execution fails immediately with an access denied error. Which two actions are required to resolve this error and run the automation successfully? (Select TWO.)
- Attach an IAM policy to the administrator's IAM identity that grants the iam:PassRole permission for the Systems Manager service role ARN.Cevap
- Configure the trust policy of the Systems Manager service role to allow the service principal ssm.amazonaws.com to assume the role.Cevap
- CAdd the iam:PassRole permission to the IAM trust policy of the EC2 instance profile to allow the Systems Manager service to pass the role to the instances.
- DModify the trust policy of the Systems Manager service role to allow EC2 instances to assume it using the STS AssumeRole API.
- EDefine a Patch Group tag key and value on the target instances and register the custom SSM document with a matching patch baseline.
Cevap
The administrator must attach an IAM policy to their own IAM identity that grants the iam:PassRole permission for the Systems Manager service role ARN, and configure the trust policy of the Systems Manager service role to allow the service principal ssm.amazonaws.com to assume the role.
Executing Systems Manager Automation using a service role requires the user to have iam:PassRole permissions for the service role. Additionally, the service role itself must trust the ssm.amazonaws.com service principal to allow the Systems Manager service to assume it.
Adım Adım Çözüm
Anahtar Kavram
IAM PassRole permissions and service trust relationships for Systems Manager Automation
Tahmini Süre:1m 30s