Without knowing what type of error is being received (i.e. is it a 401? Is it a 403? Is it a 50x?) or having any logs to review, I'll venture a guess as to what might be causing this: You would get behavior similar to this if your Cognito token expired and was not refreshed. Generally, what you can do to alleviate this is use the refresh token to "refresh" your token when the page is idle. You can find information on how to do that programmatically here. In addition -- make sure your authentication flow is not just checking if the token is present in your browser (in a cookie, for instance) but also that it is not expired -- and if it is expired force your users to re-authenticate.
I'd encourage you to retry this operation again. I'm not sure which region, or the full list of services you're using, but want to ensure you're aware of some earlier service impact that could have possibly contributed.
While signed in to your AWS account, please check go.aws/aws-hd to see if a service you're using was affected. The increased error rates in our US West (Oregon) region have now been marked as Resolved. If you continue to encounter errors not mentioned on our Health Dashboard status, please do add additional details on this thread.
— Brian D.
- How to create a private integration using an internal Application Load Balancer for an Amazon API Gateway HTTP API?AWS OFFICIALUpdated a year ago
- How can I use Meta and Amazon Cognito as identity providers to authenticate Application Load Balancer users?AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago
- EXPERTpublished 5 months ago
- EXPERTpublished a year ago