-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Region Frankfurt: Please use AWS4-HMAC-SHA256 #829
Comments
@ataraxus There are two different signature versions that are supported by S3 in various regions. Some regions only support the newest (v4) signing. There's a list of regions and what signature versions they support here: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region If possible, I'd recommend trying the aws-sdk for interacting with S3. We have API documentation on how to use the SDK to interact with S3 here: http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html Let me know if you have specific questions or issues using the AWS SDK! |
Hey @chrisradek, after reading the original documentation I got my error. If you don't specify a region the aws-sdk will use a default region 'us-east-1' which is not compatible with my target region in Frankfurt: 'eu-central-1' after having a look where to set the appropriate region in the loopback sdk i got everything working. Ticket can be closed now. Thanks again. |
Just for folks ending up on this page, here is the site to look up your region: https://docs.aws.amazon.com/general/latest/gr/rande.html |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Hey using LoopBack which itself uses pkgcloud which in the end uses aws-sdk. If I access my S3 Bucket in Frankfurt I get: "Failed InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256."
How do I use the aws-sdk with this region?
Here is the related issue on LoopBacks site: strongloop/loopback-component-storage#101
On this lib they somehow fixed it: s3tools/s3cmd#402
The text was updated successfully, but these errors were encountered: