1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Hi,
there are four types of resolution for this:
- As pointed in the Issue, you should handle 4XX Rate Limit error code gracefully
- You need to understand if the rate limiting applies to authentication or refresh of the access token. A. if Authentication, you can try to request a quota increase for Cognito , see Quotas page https://docs.aws.amazon.com/cognito/latest/developerguide/limits.html B. If refresh of the access token, you might want to increase the life time of the Access token in the User Pool, see token Expiration parameter https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-client-apps.html
- Finally if this is bad traffic DDOS you, you apply an AWS WAF WebACL to filter out traffic before reaching Cognito see https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-waf.html
beantwortet vor 9 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
It turned out to be a variant of point 1, see the updated GH issue, thanks Jeff!