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

S3 file upload #4005

Closed
suqian1988 opened this issue Feb 15, 2017 · 2 comments
Closed

S3 file upload #4005

suqian1988 opened this issue Feb 15, 2017 · 2 comments

Comments

@suqian1988
Copy link

Steps to reproduce the behavior

set header as this:
headers: {
'x-amz-acl': 'public-read',
},

upload failed with 403 error

Expected behavior

upload can success.

Actual behavior

upload failed with 403 code

@sktt
Copy link
Contributor

sktt commented Feb 20, 2017

I also had this problem, and I think it was because

This latest signature version is supported in all regions and any new regions after January 30, 2014 will support only Signature Version 4.

That includes eu-central-1 and others https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html

But knox does not support it. Automattic/knox#254

I replaced it with the official aws-sdk here: keystonejs/keystone-storage-adapter-s3#15.

Also, switching to a different region

@stennie
Copy link
Contributor

stennie commented Jun 23, 2018

This issue was resolved in the keystone-storage-adapter-s3 v2.0.0 release, which replaces the unmaintained Knox library with the official AWS JavaScript SDK.

@stennie stennie closed this as completed Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants