Skip to content
New issue

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

Is Mturk endpoint only in us-east-1? #29

Closed
shubhamagarwal92 opened this issue Oct 14, 2019 · 0 comments
Closed

Is Mturk endpoint only in us-east-1? #29

shubhamagarwal92 opened this issue Oct 14, 2019 · 0 comments

Comments

@shubhamagarwal92
Copy link
Contributor

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:

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:

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?

shubhamagarwal92 added a commit to shubhamagarwal92/simple-amt-1 that referenced this issue Oct 18, 2019
jcjohnson added a commit that referenced this issue Jan 9, 2020
Related to #29. Setting default region to us-east-1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant