Posted On: Jan 25, 2016
You can now instruct AWS CloudFormation to continue rolling back an update to your stack even after the rollback has failed. Previously, you would not be able to reinitiate a rollback of your stack after it had originally failed, requiring you to contact customer support.
Some of the common causes of a failed rollback include changing a resource in your stack outside of CloudFormation, insufficient permissions, limitation errors, or resources that have not stabilized.
Once you have remedied the cause of the failed rollback, you can instruct CloudFormation to continue rolling back the update by using the CloudFormation Management Console or the CLI. If the stack still does not successfully roll back, contact AWS customer support. Visit here to learn more.