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

Force V4 authorization for us-east-2 #76

Open
LorneFlindall opened this issue Mar 20, 2018 · 1 comment
Open

Force V4 authorization for us-east-2 #76

LorneFlindall opened this issue Mar 20, 2018 · 1 comment

Comments

@LorneFlindall
Copy link

LorneFlindall commented Mar 20, 2018

Using libs3 in us-east-1, us-west-1 and 2 work for us, but us-east-2 fails. We get Error: S3 Copy Failed : The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

Is there a way to force V4 authorization for these newer regions.
The following regions don't support Signature Version 2. You must use Signature Version 4 to sign API requests in these regions:

US East (Ohio) Region
Canada (Central) Region
Asia Pacific (Mumbai) Region
Asia Pacific (Seoul) Region
EU (Frankfurt) Region
EU (London) Region
China (Beijing) Region

@aghiles
Copy link

aghiles commented Apr 7, 2018

Make sure you are you are correctly setting the bucket_context.authRegion (in your case, set it to "us-east-2"). Not setting that member will cause these kind of errors in V4 environments.

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

2 participants