2 回答
- 最新
- 投票最多
- 评论最多
0
It is possible that they have undergone a modification and that there is another object that depends on it, the easiest way to solve it is to go to the IAM roles console and directly delete the resource, then delete the stack again and since those resources have already been eliminated will not give you a problem
0
First, you should try to get more information about why the deletion of the resource has failed:
- When you open the tab "Resources" in your CloudFormation stack (or nested stack) and compare the name, you are able to figure out what exactly failed to delete
- Typically, you see the underlying reason in the very first fail event in "Events", or in the according CloudTrail log
Resolution now depends on the underlying reason:
- If it's a dependency which only affects the current stack (like a resource with deletion policy set to RETAIN which depends on the failing resource, an S3 bucket which still has objects in it, or similar) you can delete the failing resource manually, and then re-run the stack deletion.
- If the resource is used outside of your stack and must not be deleted, update the CFN template (or use the CLI) and set the resource's deletion policy to RETAIN
See also here for more information.
已回答 9 个月前
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前