Disabled regions detection is using hardcoded region "us-east-1" that could be a disabled region in some configurations

[Rackme]

Describe the Bug

In some configurations, accounts could be regional and thus could not use the region "us-east-1", disabled by Service control policies (SCPs).

Expected Behavior

If regions are specified in the config.hcl, the use of DescribeRegions to detect disable regions should use one of them.

CloudQuery Version

cq-provider-aws v0.6.0

Debug Output

Steps to Reproduce

Use of the following configuration with an account limited to these regions :

provider "aws" {
  configuration {
    // Optional. if you want to assume role to multiple account and fetch data from them
    //accounts "<YOUR ID>" {
    // Optional. Role ARN we want to assume when accessing this account
    // role_arn = <YOUR_ROLE_ARN>
    // }
    regions = ["eu-west-3", "eu-central-1"]
    // Optional. Enable AWS SDK debug logging.
    aws_debug = true
  }

Additionnal content

I will probably do a PR for this one. I might have the time for it.

References

#39

[roneli]

Hi @Rackme, thanks for the issue, yes that makes sense we can either make it configurable to disable checking disabled regions, or create a fallback in this case to find disabled regions with regions defined from the list of regions given.

Tell me if you require any assistance with the PR.