创建CloudFormer模板及ROLLBACK_COMPLETE堆栈后的可用操作咨询

Let's break down what you can do with your CloudFormerLaunchedStack and whether it can help create new resources, based on the details you shared:

First, Understand the Stack State #

Your stack is in the ROLLBACK_COMPLETE state. This means the initial stack creation failed for some reason, and AWS CloudFormation rolled back all resources that had been successfully created during the failed deployment. Right now, the stack exists only as a deployment record—there are no active resources associated with it.

Available Actions for the Stack #

Here’s what you can do with this stack:

• Delete the stack: Since there are no active resources left, deleting it will just remove the stack’s record from your CloudFormation console/API. This is a common cleanup step for failed deployments.
• Investigate the failure cause: Check the stack’s event history (via the AWS Console, AWS CLI aws cloudformation describe-stack-events --stack-name CloudFormerLaunchedStack, or AWS SDKs) to see exactly why the deployment failed and triggered a rollback. Common issues include invalid resource configurations, insufficient IAM permissions, resource quota limits, or dependency errors between resources.
• Re-deploy the stack (with fixes): If you identify and resolve the root cause of the rollback, you can re-launch the stack using your existing template_test CloudFormer template (or a modified version of it). Just make sure to address the issues that caused the initial failure first.

Can You Create Instances/Resources With This Stack? #

Short answer: No.

The ROLLBACK_COMPLETE stack doesn’t have any active resources—all resources that were created during the failed deployment were already deleted as part of the rollback process. This stack can’t be used to launch new instances or resources directly.

If you want to create resources using your CloudFormer template, you’ll need to:

1. Figure out why the initial stack launch failed (using the stack event logs mentioned above).
2. Fix the issue (e.g., adjust template configurations, request quota increases, update IAM permissions).
3. Re-create the stack from your template_test template (which is in CREATE_COMPLETE state, so it’s a valid template).

内容的提问来源于stack exchange，提问作者styling