-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
botocore 1.9.13 resulting in 400s on s3 HeadObject if region is wrong #1413
Comments
Just confirming that we are seeing this exact bug as well. |
Can you provide debug logs for a request that fails? |
Will do. Have to obfuscate key and bucket names. Will take a second. |
I am seeing this as well:
These are my logs:
I think we may need to revert this and re-release. |
Our debug log is nearly identical to @kyleknap |
Yep I can confirm here. Let's revert this. |
PR to revert this is here: #1414 |
Thanks for the fast response and fix 🥇 |
As a note, this will fail to redirect only if the client is in the |
Will there a be a re-release or should we stick with our version freezes? |
There will be another release going out shortly that reverts the above PR. We'll need to take some time to figure out how to tighten when we redirect while still supporting redirects for clients using |
Hi, for what it's worth, I'm seeing this behaviour in us-west-2, although my own debug logs show us-east-1 for the region. My logs look exactly like the one @kyleknap posted. |
@pkmnfrk Yep, it's the region the aws cli is configured to use (for example by setting |
We just released a fix. Upgrade to |
Looks good on my end! Thanks for the quick turn around! |
No problem. Glad it works again. Closing out issue. |
Problem
Upon upgrading to awcli 1.14.60 we started to get:
when invoking
aws s3 cp
. It turns out that if our default region was not set correctly (i.e. it didn't match the region the file was actually stored in) this happens. We can fix by specifying--region
but that means we have to know the underlying region of each s3 key.Our current fix is to pin
awscli==1.14.59
which uses botocore 1.9.12 and avoids all errors. This is happening across all our local boxes and CircleCi builds.Suspicion is that #1409 might have something to do with it.
Repro
Assume
your_file.txt
is inus-west-2
aws s3 cp s3://your_bucket/your_file.txt --region us-east-1
will fail with above erroraws s3 cp s3://your_bucket/your_file.txt --region us-west-2
will succeedNote: We use
sse
liberally so I'm not sure if this repros on a key without encryption.System info
The text was updated successfully, but these errors were encountered: