- Newest
- Most votes
- Most comments
Hello.
Before looking elsewhere, it's always a good idea to take a closer look at the CloudFormation event log. Sometimes, there may be more details available in the log messages that could provide a hint about the issue.
Even if the Cognito UserPool itself hasn't changed, other resources that are dependent on it or related to it may have changed, causing the error. For example, if you have a Lambda trigger associated with the UserPool and Lambda has some changes, it might lead to a failure in updating the UserPool.
AWS CloudFormation provides a feature called Drift Detection. This allows you to detect whether the actual AWS resources have drifted from the expected configuration. You can run a drift detection on your stack and see if there's any drift detected for your Cognito UserPool or related resources.
Ensure that the IAM Role you're using with CloudFormation has the necessary permissions to update and manage Cognito UserPools. It's possible that permissions have changed or been reduced since your last successful update.
Best regards, Andrii
Relevant content
- asked a year ago
- Accepted Answerasked 23 days ago
- AWS OFFICIALUpdated 2 years ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 4 years ago