Intermittent SignatureDoesNotMatch errors using s3 cp #986
Assignees
Labels
bug
This issue is a bug.
Comments
|
Here is some maybe relevant debug info from a failed transfer: https://gist.github.com/tmont/aeaaf521e15d83aa14e2 |
|
Thanks, I believe I've isolated the issue and will have a fix shortly. |
jamesls
added a commit
to jamesls/botocore
that referenced
this issue
Nov 7, 2014
Fixes aws/aws-cli#986 The bug was that the fix_s3_host always sets the auth_path to the current path of the request.url. However, in the case of a retried request, we call fix_s3_host again which changes the auth_path to the (already modified) request path. This generates an auth error. The fix now is to check if auth_path is set, and if it is, then we can immediately return.
jamesls
added a commit
to jamesls/botocore
that referenced
this issue
Nov 7, 2014
Fixes aws/aws-cli#986 The bug was that the fix_s3_host always sets the auth_path to the current path of the request.url. However, in the case of a retried request, we call fix_s3_host again which changes the auth_path to the (already modified) request path. This generates an auth error. The fix now is to check if auth_path is set, and if it is, then we can immediately return.
|
Thanks! When is this fix slated to be released (i.e. when can I update via |
kyleknap
added a commit
that referenced
this issue
Nov 11, 2014
* release-1.6.0: Bumping version to 1.6.0 Update changelog Fix filter bug Add assumerole/waiters to the config file Fix formatting (pep8) Update waiters to use the new get_waiter_model Update waiter code based on feedback Expose waiters in the CLI Add support for MFA when assuming a role Fix integ test failure Remove commented out code Initial commit of assume role cred provider Add #986 to the changelog
thoward-godaddy
pushed a commit
to thoward-godaddy/aws-cli
that referenced
this issue
Feb 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I regularly upload a bunch of local static assets (css, js, images, etc.) to S3 as part of a deployment process and occasionally during the course of running the
aws s3 cp --recursivecommand I'll get aSignatureDoesNotMatcherror.When it happens it only happens in the middle of the process, i.e. it already successfully uploaded a dozen or so files. So I know it's not my credentials.
I can't seem to reproduce it reliably, but it's pretty annoying.
The text was updated successfully, but these errors were encountered: