Missing region in config Error Message in AWS prevents running the collection/scan

Hi,

Thanks for creating this cloud assessment tool. I am actively using it.

When running the latest code for AWS, I am getting below error hence it does not complete the scan.

*** [INFO][REGIONS] Could not load all regions from EC2: {"message":"Missing region in config","code":"ConfigError", ...} ***

After that it goes to a retry loop -

Earlier code that I have (as of Sep 30th, 2021) do run properly for the same AWS account.

Is there anything I need to do in AWS to resolve it (i.e. configure regions, enable/disable, etc.) ? Or is this potentially a bug ?

When I am running this for a client, I cannot simply ask them to enable all regions just to run the scan (assuming that is the issue).

I did try specifying regions I want (as parameters/aws config) but still get the same results.

(I see that collectior.js and regions.js have been updated somewhat and they have more checks and explicit product-region mappings in the latest code).

Thanks for looking into it.

*****

INFO: Found 273 API calls to make for aws plugins
INFO: Collecting metadata. This may take several minutes...
[INFO][REGIONS] Could not load all regions from EC2: {"message":"Missing region in config","code":"ConfigError", ...}
Trying again in: 2.808 seconds
Trying again in: 4.662 seconds
Trying again in: 5.25 seconds

********

Start with collector.js and regions.js, which the report identifies as recently changed; reproduce the AWS scan and trace the REGIONS path when the SDK reports "Missing region in config." Done means the configured or discovered region path no longer enters the retry loop and the collection completes.

Written by the indexing model from the issue text.