A SysOps Administrator is configuring an AWS Systems Manager State Manager association to run a custom script on a fleet of target Amazon EC2 instances. The target instances have the SSM Agent installed and running, and they are configured with an IAM instance profile containing the AmazonSSMManagedInstanceCore policy. The administrator configures the association to use a custom service role named StateManagerExecutionRole to perform the operations. However, when the administrator attempts to create the association, the action fails with an "Access Denied" error. What is the most likely cause of this failure?
- AThe trust policy of the StateManagerExecutionRole does not list the administrator's IAM user or role as a trusted entity to assume the role.
- BThe target EC2 instances are missing the patch group tag that is required to align them with the custom association in Systems Manager Patch Manager.
- The administrator's IAM user or role policy is missing the iam:PassRole permission for the StateManagerExecutionRole.Cevap
- DThe administrator's IAM policy grants access to the KMS key used to encrypt Systems Manager outputs, but the KMS key policy itself does not explicitly allow the administrator's IAM user.
Cevap
The administrator's IAM policy is missing the iam:PassRole permission for the StateManagerExecutionRole, preventing the user from passing the role to Systems Manager.
The correct answer is correct because creating a State Manager association that executes tasks using a custom service role requires the user to have the iam:PassRole permission for that role. Without this permission, the AWS API prevents the user from passing the role to Systems Manager, resulting in an Access Denied error during creation.
Adım Adım Çözüm
Anahtar Kavram
IAM PassRole requirement for AWS Systems Manager Service Roles
Tahmini Süre:1m 30s