-
Notifications
You must be signed in to change notification settings - Fork 32
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 tests is failing #52
Comments
Please be more specific. Did you set up credentials?
…On Fri, Nov 8, 2019, 4:33 AM fedoseiev ***@***.***> wrote:
Nothing works
failing with s3 response error *AccessDenied: Access Denied*
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#52?email_source=notifications&email_token=AAAH27MJCPDLA2IELE6K7L3QSUW5XA5CNFSM4JKUYWS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HX5FHAQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAH27J5SKSTCWGIY5QBLQLQSUW5XANCNFSM4JKUYWSQ>
.
|
So I had found a reason why it wasn't working. solution: allowing "s3:PutObjectAcl" action in bucket policy |
Thanks for pointing that out. Would you mind submitting a PR adding what
needs to be done to the README?
…On Fri, Nov 8, 2019, 9:05 AM fedoseiev ***@***.***> wrote:
So I had found a reason why it wasn't working.
I've made uploads using aws-sdk and it has succeeded.
Then by traveling in uploadfs code I've found the difference: *ACL:
'public-read'*(you have) and indeed s3 is blocking my requests because of
this.
solution: allowing "s3:PutObjectAcl" action in bucket policy
My bucket is fully open to public, but without this setting - it won't
work.
(sorry for bothering)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#52?email_source=notifications&email_token=AAAH27PT2WMNYNDMZ23LYCDQSVW3LA5CNFSM4JKUYWS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDSGSTY#issuecomment-551840079>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAH27IDYURMVNXRKXKVAO3QSVW3LANCNFSM4JKUYWSQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nothing works
failing with s3 response error AccessDenied: Access Denied
The text was updated successfully, but these errors were encountered: