Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Assume Role in non AWS Partition #1176

Closed
bbernays opened this issue Jul 6, 2022 · 1 comment · Fixed by #1177
Closed

Assume Role in non AWS Partition #1176

bbernays opened this issue Jul 6, 2022 · 1 comment · Fixed by #1177
Labels
bug Something isn't working

Comments

@bbernays
Copy link
Contributor

bbernays commented Jul 6, 2022

Describe the bug

If a user attempts to assume a role in a partition other than the AWS commercial partition CloudQuery will attempt to use the default region (us-east-1) which will fail because the credentials in the other partitions are not valid in the commercial regions

Expected Behavior

CloudQuery should have sensible defaults, but should enable users to override them

Steps to Reproduce

assume role in aws-gov region with no environment variables

Possible Solution

No response

Provider and CloudQuery version

all

Additional Context

No response

@bbernays bbernays added the bug Something isn't working label Jul 6, 2022
@bbernays bbernays changed the title Assume Role in none AWS Partition Assume Role in non AWS Partition Jul 6, 2022
@bbernays
Copy link
Contributor Author

bbernays commented Jul 6, 2022

As a workaround users can set AWS_REGION environment variable to the region they want to use for assuming the role. For example:

export AWS_REGION= us-gov-east-1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant