- Newest
- Most votes
- Most comments
Hello, I assume the subnets and security groups were created in the concerned RDS CloudFormation stack and then used in your QuickSight setup which is not managed by the RDS stack. Please clarify if this is not the case. It might impact the existing QuickSight setup if the subnets/security groups are deleted, therefore, it is recommended not to delete them. You can delete the stack by retaining the DELETE_FAILED resources (in this case, subnets/security groups) that are still in use by other resources outside the concerned CloudFormation stack. Steps to delete a stack with a dependent object or other dependencies that can't be deleted can be found here.
Thank you mate :)
I get this error after trying to delete RDS stack:
Embedded stack arn:aws:cloudformation:eu-west-2:xxxxxxxxxxxxxx:stack/cfgc-rds-prod-RdsStack-DN8FVT92INSB/6fe1a500-3445-11ed-af21-02096dbf2ed8 was not successfully deleted: The following resource(s) failed to delete: [QuicksightRDSSG, QuicksightSubnet].
In fact, I was asked to remove the entire infrastructure created by Cloudformation code pipeline and this pipeline normally deploys the following stacks: VPC, RDS, Elasticache, ECS, Cloudfront and DNS stacks. I managed to remove DNS, Cloudfront, ECS and E;lasticache stacks but when I tried to remove RDS I got these issues. I have not removed VPC yet. However, Quicksight is separate from this pipeline. This subnet and SG are part of the infrastructure that needs to be removed. All I do not want is to affect Quicksight itself.
I see in https://docs.aws.amazon.com/quicksight/latest/user/vpc-creating-a-connection-in-quicksight.html that connection of QuickSight to a VPC is optional. You'll need to remove the connection if there is one before you can complete all your other tasks, especially removing the VPC which by the way seems a pretty drastic thing to do!
Removing the connection should allow your RDS Stack to delete successfully.
Relevant content
- asked 2 years ago
- asked 5 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 4 months ago