CloudFormation Stacks Should Not Have A Failed Status
More Info:
None of your Amazon CloudFormation stacks should be in Failed mode for more than 6 hours. Any failed CloudFormation stacks that are not fixed on time can lead to application downtime, security issues or unexpected costs on your AWS bill.Risk Level
InformationalAddress
Operational MaturityCompliance Standards
CBPTriage and Remediation
Remediation
Using Console
Using Console
To remediate a CloudFormation stack with a failed status in AWS using the AWS console, follow these steps:
- Open the AWS Management Console and navigate to the CloudFormation service.
- Select the CloudFormation stack with a failed status that you want to remediate.
- Click on the “Events” tab to view the events associated with the stack.
- Review the events to identify the root cause of the failure. The event details will provide information on the resource that failed and the reason for the failure.
- Once you have identified the root cause of the failure, take the appropriate action to remediate the issue. This may involve updating the CloudFormation template, modifying the resource configuration, or resolving any dependencies or permissions issues.
- After making the necessary changes, update the CloudFormation stack by clicking on the “Update Stack” button.
- Follow the prompts to upload the updated template and apply the changes to the stack.
- Monitor the stack events to ensure that the update is successful and the stack status changes to “CREATE_COMPLETE” or “UPDATE_COMPLETE”.
Using CLI
Using CLI
To remediate the CloudFormation Stack failed status in AWS using AWS CLI, follow these steps:Replace This will provide information on the events that led to the failed status of the stack.Replace If the stack status is CREATE_COMPLETE or UPDATE_COMPLETE, then the remediation is successful. If not, repeat steps 2 to 4 until the stack status is successful.
- Identify the CloudFormation Stack that has a failed status by running the following command in the AWS CLI:
<stack-name> with the name of the CloudFormation Stack that has a failed status.- Check the events associated with the failed stack by running the following command:
- Fix any issues that caused the stack to fail. This may involve updating the CloudFormation template or fixing any resource dependencies.
- Once the issues are fixed, update the stack by running the following command:
<stack-name> with the name of the CloudFormation Stack that has a failed status, <path-to-template-file> with the path to the updated CloudFormation template file, and <path-to-parameters-file> with the path to the updated parameters file.- Wait for the stack to update and check its status by running the following command:
Using Python
Using Python
To remediate the “CloudFormation Stacks Should Not Have A Failed Status” misconfiguration in AWS using Python, you can follow the below steps:Note: Make sure to test the CloudFormation template before updating the stack(s) to avoid any further misconfigurations.
- First, you need to identify the CloudFormation stack(s) that have a failed status. You can use the
boto3library in Python to get the list of CloudFormation stacks and their status.
- Once you have identified the failed stacks, you can delete them using the
delete_stackmethod of the CloudFormation client.
- You can also update the CloudFormation template and re-create the stack(s) to remediate the misconfiguration.