- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
When deleting the stack there's the option to retain resources - in this case the RolePolicy - up until now I've been trying to delete it along with the stack. I've been playing around with the AWS CLI to see if I could find the policy and somehow delete it via CLI, with no luck. I reasoned that maybe the policy doesn't actually exist, so if I choose to keep it when deleting the stack, Cloudformation won't attempt to delete the faulty or non-existent policy and will succeed at deleting the stack. That seems to have done the trick.
Maybe there's a bug somewhere, but not one that creates a RolePolicy with no name, but instead one that tried to delete a RolePolicy that a) doesn't exist, and b) has no name.
As far as I can tell, there are no extraneous RolePolicy objects in IAM associated with my account, so I assume I'm good to go!
Hello.
what about manually deleting the target resource from the management console before deleting the CloudFormation template?
Is it possible to try to delete the CloudFormation template after manually deleting it?
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
I've tried deleting from console. I can't delete the Cloudformation resource because of the aforementioned error, and I can't find the RolePolicy in IAM to delete it (and circumvent the error in Cloudformation.) I tried deleting the Role manually, too, which succeeded but didn't help.