We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi @jcjohnson ,
Thanks for this cool repo. :)
I want to know if the region that we specify for AMT is fixed for us-east-1. I see that you have the enpoint_url hardcoded for us-east-1.
us-east-1
If I don't mention the region at all, I get:
botocore.exceptions.NoRegionError: You must specify a region
But, if I mention my default region as us-west-1 (using aws configure), I am getting the error as:
us-west-1
aws configure
An error occurred (InvalidSignatureException) when calling the CreateHIT operation: Credential should be scoped to a valid region, not 'us-west-1'.
Is this the reason that we don't specify region in the config files?
region
The text was updated successfully, but these errors were encountered:
Related to jcjohnson#29. Setting default region to us-east-1
3a44226
Merge pull request #30 from shubhamagarwal92/master
3001e1a
Related to #29. Setting default region to us-east-1
No branches or pull requests
Hi @jcjohnson ,
Thanks for this cool repo. :)
I want to know if the region that we specify for AMT is fixed for
us-east-1
. I see that you have the enpoint_url hardcoded for us-east-1.If I don't mention the region at all, I get:
But, if I mention my default region as
us-west-1
(usingaws configure
), I am getting the error as:Is this the reason that we don't specify
region
in the config files?The text was updated successfully, but these errors were encountered: