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

Common mutipart signature auth error can cause multipart uploads to fail #696

Open
ggprod opened this issue Jan 31, 2024 · 1 comment
Open

Comments

@ggprod
Copy link

ggprod commented Jan 31, 2024

Common multipart uploads fail with an error like:
ERROR "cp **** s3://****": MultipartUpload: upload multipart failed upload id: dBmwIX7UhK9IotwKi1j1bM.sInQ7jUngrmjZ3GlmNz1GfLmYZ_4b94ReAgZ4OOMm0wQUfm2DQshNxlCyTBFuzlOfMWKnMLIhEYVB7p5iw39vMcNJn375vBDhWH069xCaa24d8SyktuEyNR5jIt.EOGp9fiucRRtXZ9l80.UnARw- caused by: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method. status code: 403, request id: H871REM5J5C1BNN0, host id: FE1FVxCXCymin8yLl1DfjNAyx/yWqS9MwSQ0b7Tcum5xEeoMo/nbpZOjqgEtdnsx2XrDFqrR6/0=

Typically re-uploading the failed object succeeds. It may be good to add retries for this type of error (even though it is a typically non-retry auth error)

I should add this was observed uploading to an s3 bucket with transfer acceleration enabled using a command like this:
s5cmd --endpoint-url https://****.s3-accelerate.amazonaws.com --numworkers 512 cp --destination-region eu-central-1 --concurrency 512 **** s3://*****

@ggprod ggprod changed the title Occasional mutipart signature auth error can cause multipart uploads to fail Common mutipart signature auth error can cause multipart uploads to fail Jan 31, 2024
@atamano
Copy link

atamano commented Feb 1, 2024

I'm having the same issue with R2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants