Issue Summary

When importing Insight objects using AWS, if the user is syncing with too many accounts and combine with many regions, the test configuration will show as spinning forever on UI which prevents from going to the next step. This is due to the backend API is timing out due to testing too many AWS connections at the same time.

Steps to Reproduce

1. Go to an Insight Object Schema. Go to Object Schema Configuration.
2. Go to Import Tab, Create new Import, select  AWS Import.
3. Enter an import name and click next steps.
4. Fill in AWS Access Key and AWS Access Token.
5. In regions, select about 4 regions such as Sydney, Singapore, US, EU
6. In Roles ARN, enter at least 10 roles from 10 different accounts
7. In Account List, enter about 10 different accounts of the above roles
8. Open Developer Inspection tool, go to the Network tab.
9. Click Test Configuration, you will see that the API requests to `insight-aws-import` will take more than 1 minute to run and then timeout.
10. The UI will keep showing the loading spinning icon forever even that the request is already timeout.

Expected Results

• It should not timeout and when the testing API is finished, it should proceed to the next step.
• If it's actually timeout for some reason, the UI should show an error, hide the loading spinning icon and let the user try again.

Actual Results

• The UI will keep showing the loading spinning icon forever even that the request is already timeout.

Workaround

• Rather than selecting multiple AWS regions in one big import with many accounts, try to choose only 1 Region at a time, this will make the test API run faster without timing out and the user can still proceed to the next step. Then repeat the step to create a new import for each was region.

Fix

Update to version 2.2.20 of the Assets - AWS Integration marketplace app.

For some additional tips on optimising your configuration:

1. Even though isolated (iso) regions can be configured, the import app doesn't support them as there is no way to configure the custom endpoint for them. Having isolated regions configured in your import may significantly impact import times.
2. If there are any roles included in the configuration that the configured API key and secret does not have permission to assume, this may significantly impact import times.
3. If there are any Object Type (selectors) enabled in the import which the configured API key and secret does not have access to describe the resources for, this may significantly impact import times.

If you still have issues with the configuration hanging after trying 2.2.20, enable logging for the AWS import app:

1. Log in as a user with the JIRA System Administrators global permission.
2. Navigate to Administration > System > Logging and profiling
3. Under the "Default Loggers" section, click on Configure logging level for another package
4. At the "Package name" field, insert com.riadalabs.jira.plugins.aws
5. At the "Logging Level" dropdown, select TRACE'

After enabling the logging, try to edit and save your configuration again, the logs may be able to provide some additional insights.