An administrator is troubleshooting a failed stack update in AWS CloudFormation. The stack has entered the UPDATE_ROLLBACK_FAILED state. The update failed due to a misconfiguration in an Amazon EC2 launch template, and the subsequent rollback failed because the IAM service role originally associated with the stack was accidentally deleted.
Which combination of actions must the administrator take to successfully roll back the stack to a stable state? (Select TWO.)
- Ensure the administrator's IAM identity is granted the iam:PassRole permission for the IAM service role to be used for the rollback.Cevap
- Execute the continue-update-rollback command, specifying the ARN of the IAM service role.Cevap
- CModify the CloudFormation stack template to remove the misconfigured EC2 launch template, then execute the update-stack command.
- DExecute the rollback-stack command, specifying the --service-role parameter to force the rollback using a different role.
- EAdd the sts:AssumeRole permission for the service role directly to the administrator's IAM policy to allow CloudFormation to execute.
Cevap
The administrator must ensure their IAM identity is granted the iam:PassRole permission for the service role and execute the continue-update-rollback command specifying the ARN of that service role.
The correct options are: granting the administrator the iam:PassRole permission and executing the continue-update-rollback command with the role ARN. When a service role associated with a stack is deleted, any attempt to roll back will fail because CloudFormation cannot assume the role. The administrator can resolve this by providing a new or recreated role during the continue-update-rollback command. To do this, the administrator's identity must possess the iam:PassRole permission for the new role so CloudFormation can assume it.
Adım Adım Çözüm
Anahtar Kavram
Remediating CloudFormation stacks in the UPDATE_ROLLBACK_FAILED state by specifying an alternative or recreated service role.