- Más nuevo
- Más votos
- Más comentarios
It seems like the stack deletion failed due to some resources being manually deleted beforehand.
Check if any IAM roles created for the stack resources are still present. Deleting dependent roles can cause deletion failures. Recreating roles with the same name may resolve it.
Look for resources in the DELETE_IN_PROGRESS state using the AWS console or CLI. Wait for these to complete deletion before retrying stack deletion.
Examine the CloudFormation event logs using AWS CloudTrail to identify the failed API operations during deletion. This may provide clues on which resources are blocking deletion.
Consider updating the stack template to remove references to already deleted resources before attempting deletion again. AWS CDK allows setting removal policies to avoid orphaned resources.
As a last resort, delete the stack forcefully using the --force
option in the AWS CLI. This bypasses dependency checks and can remove stuck stacks, but use with caution.
Let me know if deleting gets stuck again.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
The thing is the stack was in the process of creation. And at one point the resources started returning "CREATE_FAILED" status without any comments in the CloudFormation. So it's really a mystery of a kind. We didn't initiate the stack deletion and didn't delete any resources manually.