Internal Server Error when calling /resources endpoint

Describe the bug When trying to load you are presented with a “We could not load resource configuration” error banner. When invoking the /resources endpoint via API Gateway itself, this returns the following error:

Endpoint response body before transformations: {"errorMessage":"Response payload size (9873641 bytes) exceeded maximum allowed payload size (6291556 bytes).","errorType":"Function.ResponseSizeTooLarge"}

This means that the payload size returned by this function is larger than the default 6Mb limit.

To Reproduce Steps to reproduce the behavior: I guess this will be related to the amount of accounts / regions and resources. We currently have 10 imports from a number of accounts / regions.

Expected behavior Not to throw an error and become unusable. Perhaps this should page the response back or not use lambda to read from the DB Screenshots If applicable, add screenshots to help explain your problem.

Browser (please complete the following information):

• Chrome
• Version 85.0.4183.83 (Official Build) (64-bit)

Additional context Add any other context about the problem here.

[StewartW]

Hey @svozza thanks for the work around. I’ve noticed that if I just filter it out certain accounts it becomes usable again.

[svozza]

Hi there, thanks for raising this issue. What looks like is happening is that there are so many resources being returned by the initial query to populate the Resources sidebar that it is exceeding the lambda payload limit. Unfortunately, the only workaround I have currently is to remove one of the imported accounts to bring that number down. We are currently investigating pagination strategies to mitigate this (this is a non-trivial problem with graph databases) for the next release.

As @StewartW has pointed out, the current workaround is to filter out certain accounts in the UI rather than removing the account entirely.