Cloudformation Stack issues removing it

0

Hi,

We have an infrastructure Codepipeline with a number of stacks such as VPC, RSD, ECS, Cloudfront and DNS. We had some weird errors in the pipeline in a way I have tried to remove all the Cloudformation stacks to try to recreate a fresh pipeline. However the only Cloudformation stack left with errors after trying to remove it is the following RDS stack and I could not see how to fix it:

2022-11-23 14:52:07 UTC+0000 Crafter-RDS-Test ROLLBACK_COMPLETE - 2022-11-23 14:52:06 UTC+0000 RdsStack DELETE_COMPLETE - 2022-11-23 14:51:55 UTC+0000 RdsStack DELETE_IN_PROGRESS - 2022-11-23 14:51:42 UTC+0000 Crafter-RDS-Test ROLLBACK_IN_PROGRESS The following resource(s) failed to create: [RdsStack]. Rollback requested by user. 2022-11-23 14:51:42 UTC+0000 RdsStack CREATE_FAILED Embedded stack arn:aws:cloudformation:eu-west-1:XXXXXXXXXXXX:stack/Crafter-RDS-Test-RdsStack-1F1EM487W2KQ5/4364b050-6b3e-11ed-88aa-0664e7728df7 was not successfully created: The following resource(s) failed to create: [DBSubnetGroup]. 2022-11-23 14:51:08 UTC+0000 RdsStack CREATE_IN_PROGRESS Resource creation Initiated 2022-11-23 14:51:07 UTC+0000 RdsStack CREATE_IN_PROGRESS - 2022-11-23 14:51:02 UTC+0000 Crafter-RDS-Test CREATE_IN_PROGRESS User Initiated

Can anyone help please.

Thanks in advance

2 Answers
0

Hello, from the events posted, I assume Crafter-RDS-Test is the root stack and RdsStack is the nested stack. The root stack is in ROLLBACK_COMPLETE state, which means a successful removal of one or more stacks after a failed stack creation or after an explicitly canceled stack creation, when in this state, you should be able to delete the stack. The nested stack is in DELETE_COMPLETE state, which means it was successfully deleted too. What error(s) do you see if you delete the root stack at this state?

AWS
SUPPORT ENGINEER
answered 2 years ago
  • Thank you. When I remove the root stack "Crafter-RDS-Test" it is removed and no nested stack is left and when I re-run the pipeline I get those same errors described already. I don't understand why.

0

Hello, so the issue here is, because the nested stack failed to create, the root stack creation also failed and eventually started to rollback. Per the events above, the reason why the nested stack failed to create is because, a resource with logical ID DBSubnetGroup failed to create, please review the events in the nested stack to identify why it is failing to create this resource, that is, in your case, review events of stack with name Crafter-RDS-Test-RdsStack-XXXXX.

Note: If you need granular review of your environment, we require details that are non-public information. Therefore, kindly open a support case with AWS using the following https://console.aws.amazon.com/support/home#/case/create

AWS
SUPPORT ENGINEER
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions