TEAM application crashing when creating an Eligibility Policy

[vgsachin839]

Describe the bug
We have deployed the TEAM application in our LZ Organization, which is having more than 1000+ AWS accounts and 750+ permission sets in Identity Center. When we are trying to create an eligibility policy, UI is crashing, and we are seeing the errors in Developer Tools console in browser. We tested with both Chrome and Edge.

Is it due to the volume of accounts and permission sets, this issue is happening ?

Expected behavior
Data like Org accounts, OUs and Permission Sets should be loaded successfully in the Eligibility Policy screen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11

• Browser: Chrome

• Version: Chrome Version 125.0.6422.142 (Official Build) (64-bit)

• OS: Windows 11

• Browser: Edge

• Version: Edge Version 125.0.2535.85 (Official build) (64-bit)

[AlDawoode]

Hi,
I'm facing similar issue when creating an Eligibilty Policy.
The UI doesn't crach directly when i click on "Create eligibility policy", but it does after 20 second where it can't load AWS OUs

[AlDawoode]

For now i fixed my issue by the following steps:

• I print out the error msg in the console when the UI crash
  

• I checked the lambda that fetch the AWS OUs and it work fine BUT it just take time because i have a big number of OUs so lambda does take 44 seconds in my case.

• That Frontend part (ReactJS) make a request to the backend (AWS AppSync) it is just an api that invoke lambda function and return the response back to the frontend

So the issue comming from AppSunc
It turns out that Appsync has a 30 second hard limit for request execution time for mutations, queries, and subscriptions.
Please refer to the Appsync documentation for this limit.
Unfortunately, this means that there is no configuration or setting which will allow us to exceed this limit.

If you have a query that is taking more than 30 seconds, then the workaround is to implement this in an asynchronous manner. Please refer to this blog for a strategy in Implementing a long-running query on AWS AppSync

The above suggestion solution will take much time and effort for me to do..
AWS should re-implement the way of fetching OUs, Groups, Users, and Permission Sets by following the above suggestion or coming with better one.

• For now, my workaround involved updating the lambda function (teamgetOUs/src/index.py) to return a list of specific OUs, either dynamically generated or hardcoded.

[tawoyinfa]

@AlDawoode this is in the backlog and would be implemented as soon as we resolve #236

[AlDawoode]

@tawoyinfa
The first bug i was facing is the one you mentioned #236 :)
and i followed the workaround suggestion you mentioned there .. Thanks.

Another bug i faced when i deployed the AWS TEAM solution is that the UI crach on login page.
An error appear In the google chrome --> inspect ---> console :
Amplify has not been configured correctly

It turns out that some packages has duplicate versions:
I fixed that by downgrading/upgrading some packages.

Upgrading all packages to latest version doesn't help.
Note: i still have packages that has duplicate versions:

• @aws-amplify/graphql-transformer-core
• @aws-amplify/graphql-transformer-interfaces

[tawoyinfa]

@vgsachin839 this issue has been fixed in the latest release. Follow the guidance in the documentation to upgrade to the latest version

[vgsachin839]

@tawoyinfa I see that the issue is still not fixed even after upgrading the solution to 1.1.2. I think you have fixed the getOUs issue mentioned in issues #235, but we are still facing issue with getPermissions while creating the Eligibility policy (please refer the screenshot below). I have raised a new issue #274 for this.