-
Notifications
You must be signed in to change notification settings - Fork 155
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
Working with new Amazon S3 Regions doesn't work due to missing V4 authentication scheme #101
Comments
Same issue here. |
I hade a quick glance onto the impl. it seems to be an upstream issue. loopback-component-storage uses internally pkgcloud: https://www.npmjs.com/package/pkgcloud |
Hey @philippdhh, I fixed it for me now. See here whats was the issue: aws/aws-sdk-js#829 var publicHandler = new StorageService(
{
provider: 'amazon',
region: "eu-central-1",
keyId: "",
key: ""
}); I think it can be closed now |
Thank you very much. |
so did it worked for you? |
@philippdhh did @ataraxus' solution work? I am going to close the issue, but please re-open the issue and mention me directly if the problem persists! |
Hi,
while the loopback-component-storage seems to work well with most AWS S3 regions it does not work with regions created later than 2014 like the Frankfurt region in Europe.
The following error is returned:
{
"error": {
"name": "InvalidRequest",
"status": 400,
"message": "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.",
"code": "InvalidRequest",
"time": "2015-12-02T23:30:05.289Z",
"statusCode": 400,
"retryable": false,
"retryDelay": 60,
"stack": "InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.\n at Request.extractError (C:\Users\Philipp\WebstormProjects\GroupTravelMgrJs\node_modules\loopback-component-storage\node_modules\pkgcloud\node_modules\aws-sdk\lib\services\s3.js:343:35)\n at Request.callListeners
[........]
}
}
It seems to be related to this issue: http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4
Best,
Philipp
The text was updated successfully, but these errors were encountered: