You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After implementing the AWS Organization integration, there will be users who may have thousands of accounts in their org that will be imported by the discovery process. This greatly increases the chance that we will exceed the lambda payload limit when returning the list of accounts on the frontend. As the accounts are store in DynamoDB we cannot use the same pagination strategy as our other APIs and must instead use LastEvaluatedKey field detailed in the DynamoDB docs. This will impact on #396, as moving the organizations:ListAccounts API calls to the Settings lambda could cause rate limiting issues when calling that API repeated during paged requests.
The text was updated successfully, but these errors were encountered:
After implementing the AWS Organization integration, there will be users who may have thousands of accounts in their org that will be imported by the discovery process. This greatly increases the chance that we will exceed the lambda payload limit when returning the list of accounts on the frontend. As the accounts are store in DynamoDB we cannot use the same pagination strategy as our other APIs and must instead use LastEvaluatedKey field detailed in the DynamoDB docs. This will impact on #396, as moving the
organizations:ListAccounts
API calls to the Settings lambda could cause rate limiting issues when calling that API repeated during paged requests.The text was updated successfully, but these errors were encountered: