An organization uses AWS Service Catalog to distribute standardized infrastructure templates. The central hub account shares a portfolio with several spoke accounts. In one of the spoke accounts, the SysOps administrator creates a local launch constraint for a product in the shared portfolio. This launch constraint specifies a local IAM role named CustomProvisioningRole that possesses all necessary permissions to create the required resources. When a developer in the spoke account tries to launch the product, the deployment immediately fails, and the developer receives an error indicating that they do not have permission to perform the action. Which action must the administrator take to resolve this issue?
- Attach an IAM policy to the developer's IAM identity in the spoke account that grants the iam:PassRole permission for the CustomProvisioningRole.Cevap
- BModify the trust policy of the CustomProvisioningRole in the spoke account to allow the developer's IAM identity to perform the sts:AssumeRole action.
- CConfigure the KMS key policy of the encryption key in the hub account to explicitly allow the developer's IAM identity in the spoke account to decrypt deployment artifacts.
- DWait for the CloudFormation stack status to transition to ROLLBACK_FAILED, then manually delete the resource stack in the spoke account before attempting to re-provision the product.
Cevap
Attach an IAM policy to the developer's IAM identity in the spoke account that grants the iam:PassRole permission for the CustomProvisioningRole.
To use a launch constraint, the user or role launching the product must have the iam:PassRole permission for the role specified in the constraint. This permission allows the user to pass the role to AWS Service Catalog, which then assumes the role to provision resources on behalf of the user.
Adım Adım Çözüm
Anahtar Kavram
AWS Service Catalog Launch Constraints and IAM Role Delegation