Use the regions in specified in the teleport config instead of the environment for discovery bootstrap

[lxea]

Fixes a MIssingRegion error that would sometimes occur when running the discovery bootstrap command

❌[AWS] Create SSM Document "TeleportDiscoveryInstaller"... failed.
Failure reason: MissingRegion: could not find region configuration
ERROR: bootstrap failed to execute, check logs above to see the cause

[marcoandredinis]

I just tested this and it now works:

$ teleport discovery bootstrap --config teleport.yaml --attach-to-role MarcoAutoRoleForDiscoveryBootstrap --policy-name MarcoTestEC2DiscoveryBootstrap
Reading configuration at "teleport.yaml"...
......

Confirm? [y/N]: y
✅[AWS] Create IAM Policy "MarcoTestEC2DiscoveryBootstrap"... done.
✅[AWS] Create IAM Policy "MarcoTestEC2DiscoveryBootstrapBoundary"... done.
✅[AWS] Attach IAM policies to "MarcoAutoRoleForDiscoveryBootstrap"... done.
✅[AWS] Create SSM Document "MarcoTeleportDiscoverySSMDocInstaller"... done.

[lxea]

friendly ping when you get the chance @xacrimon @strideynet

[public-teleport-github-review-bot]

@lxea See the table below for backport results.

Branch	Result
branch/v12	Failed
branch/v13	Create PR
branch/v14	Create PR