Avoid rate limit errors on Cognito auth endpoints

0

Hello re:Post community, here's my first post.

A while ago I implemented S3 bucket support for a genomics visualization package called IGV:

https://github.com/igvteam/igv/pull/620

Today, I'm facing some problem reports w.r.t API endpoint quota limits and I'd like to hear your advice:

https://github.com/igvteam/igv/issues/1311#issuecomment-1716974095

What's the best way to mitigate or solve this issue that other partners are facing? So far, our facility hasn't seen those, but there's no reason they cannot appear in the future, generating a DoS situation for our staff and their legitimate login attempts :/

1개 답변
1
수락된 답변

Hi,

there are four types of resolution for this:

  1. As pointed in the Issue, you should handle 4XX Rate Limit error code gracefully
  2. 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
  3. 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
AWS
답변함 8달 전
profile picture
전문가
검토됨 8달 전
  • It turned out to be a variant of point 1, see the updated GH issue, thanks Jeff!

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠