- Newest
- Most votes
- Most comments
When a CloudFormation stack is in the UPDATE_ROLLBACK_IN_PROGRESS state, it means CloudFormation is actively trying to roll back changes from a failed update. For your Amplify project's stack, here's how you can address this issue:
First, you need to wait for the rollback to complete naturally. CloudFormation should automatically transition from UPDATE_ROLLBACK_IN_PROGRESS to UPDATE_ROLLBACK_COMPLETE once the rollback finishes. This can take some time depending on the resources involved.
If the stack gets stuck in UPDATE_ROLLBACK_FAILED state instead of completing the rollback, you can use the continue-update-rollback command:
aws cloudformation continue-update-rollback --stack-name amplify-myvillageprojectadmi-dev-04552
This command helps when CloudFormation can't roll back all changes after a failed stack update, often because it's trying to roll back to resources that no longer exist.
If specific resources are causing the rollback to fail, you can skip them using the --resources-to-skip parameter with the continue-update-rollback command. However, be aware that skipping resources can result in inconsistencies between your stack and actual resources, which may cause future updates to fail.
Once your stack reaches the UPDATE_ROLLBACK_COMPLETE state, you should be able to use Amplify CLI commands again. At this point, you can:
- Run
amplify pullto sync your local environment with the cloud resources - Make your schema changes incrementally rather than all at once
- Test each change with
amplify push
If you continue to face issues after the stack reaches UPDATE_ROLLBACK_COMPLETE, you might need to:
- Check CloudWatch logs for specific error details
- Verify IAM permissions for the roles used by Amplify
- Consider reaching out to AWS Support if the problem persists
Remember that making smaller, incremental changes to your GraphQL schema can help avoid these types of failures in the future.
Sources
ContinueUpdateRollback - AWS CloudFormation
continue-update-rollback — AWS CLI 2.27.41 Command Reference
Troubleshooting CloudFormation - AWS CloudFormation
answered a year ago
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 4 years ago

The above mentioned information is correct.
I tried already above but not worked any of above solution