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

Large file uploads fail with 403 Forbidden #7786

Closed
cyberduck opened this issue Feb 11, 2014 · 1 comment
Closed

Large file uploads fail with 403 Forbidden #7786

cyberduck opened this issue Feb 11, 2014 · 1 comment
Assignees
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Milestone

Comments

@cyberduck
Copy link
Collaborator

4dfbfcc created the issue

Hi,

After upgrading from 4.3 to 4.4.3, S3 uploads of files larger then ~500MB fail with 403 Forbidden.
I've tested with the same credentials, files and bucket and it's working in 4.3.1

Here is the log:

GET / HTTP/1.1
Date: Tue, 11 Feb 2014 15:07:30 GMT
Authorization: AWS AKIAIS5M73ZQSVM2CSFQ:VpWPo9hH5iyJ7srXVG4IDje1Fb0=
Host: s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.4.3 (Mac OS X/10.8.5) (x86_64)
HTTP/1.1 200 OK
x-amz-id-2: nTYdl9IVqC+9FCVTPzEx87pJKFgCMb2vxDwcVKuXjMGzC5spvFCi+jWuLVWFOmhn
x-amz-request-id: 455546FD51DAEA38
Date: Tue, 11 Feb 2014 15:07:32 GMT
Content-Type: application/xml
Transfer-Encoding: chunked
Server: AmazonS3
GET /?prefix=koce%2FCentOS-6.5-x86_64-LiveCD.iso&uploads HTTP/1.1
Date: Tue, 11 Feb 2014 15:07:31 GMT
Authorization: AWS AKIAIS5M73ZQSVM2CSFQ:VraQFKdbD3EGMMpc09rPibIT6F0=
Host: pbs-ingest.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.4.3 (Mac OS X/10.8.5) (x86_64)
HTTP/1.1 403 Forbidden
x-amz-request-id: 400E0AF5869852E2
x-amz-id-2: 3kenflrCdpmlGa1OPfrgKkzSeO1/YH/pbCLmff+Lj2mCbonP4u6npD1X9vP8viT9
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Tue, 11 Feb 2014 15:07:31 GMT
Server: AmazonS3

Thanks.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I suspect this is a IAM user that is missing a full read policy grant for the bucket. We are using multipart uploads for files larger than 100MB that requires to list existing multiparts in the bucket.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants