SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

[orimboolak]

Keep getting this error when i try to retrieve the saved image via url. Kindly help

[DevMaxIT]

Could you figure out a solution?

[buddylindsey]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

---

I am moving this chart up from below to help give more visibility to it.

Region	Setting
us-east-1	default or AWS_S3_SIGNATURE_VERSION = "s3v4"
us-east-2	AWS_S3_ADDRESSING_STYLE = "virtual"
ap-northeast-1	AWS_S3_SIGNATURE_VERSION = "s3v4"
ap-southeast-2	AWS_S3_ADDRESSING_STYLE = "virtual"
ap-south-1	AWS_S3_ADDRESSING_STYLE = "virtual"
eu-central-1	AWS_S3_ADDRESSING_STYLE = "virtual"
eu-central-1	AWS_S3_ADDRESSING_STYLE = "virtual" AWS_S3_ENDPOINT_URL = 'https://s3.eu-central-1.amazonaws.com'
eu-west-1	AWS_S3_SIGNATURE_VERSION = "s3v4" AWS_S3_ADDRESSING_STYLE = "virtual"
eu-west-2	AWS_S3_ADDRESSING_STYLE = "virtual"
eu-west-3	AWS_S3_ADDRESSING_STYLE = "virtual"
ca-central-1	AWS_S3_ADDRESSING_STYLE = "virtual"

Based on a comment make sure you are up-to-date with the latest version of this package.

[ghost]

Spend 5 hours and this worked for me, @buddylindsey solution didn't worked for me AWS_DEFAULT_ACL = 'private' AWS_S3_SIGNATURE_VERSION = 's3v4'

[buddylindsey]

@AchintyaRanjanChaudhary what region where you in and version of boto3? I found those settings, but the version of boto3 I had was already using s3v4.

[rozeweb]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

Your a life saver!!! Thanks.

[ghost]

@buddylindsey boto version --> boto3==1.13.13 AWS region -->ap-northeast-1 django-storage --> django-storages==1.9.1

[buddylindsey]

So it looks like so far

Region	Setting
us-east-1	default or AWS_S3_SIGNATURE_VERSION = "s3v4"
us-east-2	AWS_S3_ADDRESSING_STYLE = "virtual"
ap-northeast-1	AWS_S3_SIGNATURE_VERSION = "s3v4"
eu-central-1	AWS_S3_ADDRESSING_STYLE = "virtual"
eu-west-2	AWS_S3_ADDRESSING_STYLE = "virtual"
eu-west-3	AWS_S3_ADDRESSING_STYLE = "virtual"

If we get more variations from people or other regions I can update this table.

[ghost]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

I love you.

[hi-18-K]

getting this error again and again..none of the above worked..but observed that url of file from website does not contain "Amz-Security-Token" field..how to resolve that?

[krystofbe]

AWS_S3_ADDRESSING_STYLE = "virtual" also works for eu-central-1

[Psyborgs-git]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

Dude! This Totally worked thanks.

[aureliendebord]

AWS_S3_ADDRESSING_STYLE = "virtual"

Also works for eu-west-3

[davidysoards]

Added a new, identical setting bucket in region us-east-2 for use in dev only, and had to add AWS_S3_ADDRESSING_STYLE = "virtual" thanks @buddylindsey 1st bucket worked without it, but also works with it. 🤷🏻‍♂️ The first bucket didn't work until I added AWS_S3_SIGNATURE_VERSION = "s3v4", but the new one works with or without it. Not sure if the 1st still needs AWS_S3_SIGNATURE_VERSION too, but I'm leaving it for now.

Is it django-storages causing all these inconsistencies or AWS?

[gcmestre]

First of all thank you. This answers really helped. Second: I have a bucket at us-east-1 and the default didn't work neither the WS_S3_ADDRESSING_STYLE = "virtual". What it worked was AWS_S3_SIGNATURE_VERSION = "s3v4"

[dunderJB]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

Dude i love you tks !!!

[Vinay-Indoria]

@buddylindsey Thanks alot

AWS_S3_ADDRESSING_STYLE = "virtual"

worked for us-east-2

[adamcharnock]

AWS_S3_ADDRESSING_STYLE = "virtual" worked for eu-west-2. Thank you! ♥️

[shdigitalpy]

Many thanks for this info. This saved me another hour of searching through code

[vinodkr494]

AWS_S3_ADDRESSING_STYLE = "virtual" worked for eu-west-2. Thank You..

[dinie]

AWS_S3_ADDRESSING_STYLE = "virtual"

Works for ap-southeast-2. Thank you!

[ZackPlauche]

I tried all of these solutions for the correct timezones and for some reason it's still not working 🤦‍♂️ I've triple checked my keys and tried both:

AWS_S3_ADDRESSING_STYLE = "virtual"

and

AWS_S3_SIGNATURE_VERSION = "s3v4"

one at a time and even at the same time.

I made a new bucket under us-east-1 just because that's what was shown in other answers and it still didn't work with either settings.

[Ram-95]

This works for the region - ap-south-1

AWS_S3_ADDRESSING_STYLE = "virtual"

[PirateDevCom]

So it looks like so far Region Setting us-east-1 default or AWS_S3_SIGNATURE_VERSION = "s3v4" us-east-2 AWS_S3_ADDRESSING_STYLE = "virtual" ap-northeast-1 AWS_S3_SIGNATURE_VERSION = "s3v4" eu-central-1 AWS_S3_ADDRESSING_STYLE = "virtual" eu-west-2 AWS_S3_ADDRESSING_STYLE = "virtual" eu-west-3 AWS_S3_ADDRESSING_STYLE = "virtual"

If we get more variations from people or other regions I can update this table.

"virtual" setting works for ca-central-1 as well.

[asdfractal]

While troubleshooting student projects I have found that this is caused by there being a / in the secret access key. I didn't know about these settings but generating new credentials without the / would solve it.

[radupm]

This also works for eu-west-1:

AWS_S3_SIGNATURE_VERSION = "s3v4"
AWS_S3_ADDRESSING_STYLE = "virtual"

[JMIdeaMaker]

None of these worked for me. us-east-2

Edit: Updating from storages 1.9 to 1.13.1 fixed this error

[misterpip]

When using eu-central-1:

i used AWS_S3_ADDRESSING_STYLE = "virtual"

but still got an error. Adding an Endpoint + Addressing style solved it for me AWS_S3_ENDPOINT_URL = 'https://s3.eu-central-1.amazonaws.com'

[milenmihaylov]

I had this issue with a bucket in us-east-2. Without going into the last 2 hours of archeology of boto3 issues and storages code. I solved it by setting the following in my settings.py.

AWS_S3_ADDRESSING_STYLE = "virtual"

I am moving this chart up from below to help give more visibility to it.

Region Setting us-east-1 default or AWS_S3_SIGNATURE_VERSION = "s3v4" us-east-2 AWS_S3_ADDRESSING_STYLE = "virtual" ap-northeast-1 AWS_S3_SIGNATURE_VERSION = "s3v4" ap-southeast-2 AWS_S3_ADDRESSING_STYLE = "virtual" ap-south-1 AWS_S3_ADDRESSING_STYLE = "virtual" eu-central-1 AWS_S3_ADDRESSING_STYLE = "virtual" eu-central-1 AWS_S3_ADDRESSING_STYLE = "virtual" AWS_S3_ENDPOINT_URL = 'https://s3.eu-central-1.amazonaws.com' eu-west-1 AWS_S3_SIGNATURE_VERSION = "s3v4" AWS_S3_ADDRESSING_STYLE = "virtual" eu-west-2 AWS_S3_ADDRESSING_STYLE = "virtual" eu-west-3 AWS_S3_ADDRESSING_STYLE = "virtual" ca-central-1 AWS_S3_ADDRESSING_STYLE = "virtual" Based on a comment make sure you are up-to-date with the latest version of this package.

For eu-central-1 you need both settings as they are. Cheers buddy! You got a beer from me.

[MarcinR1989]

For eu-central-1 I needed to set 3 mentioned before variables: AWS_S3_ADDRESSING_STYLE = "virtual" AWS_S3_ENDPOINT_URL = 'https://s3.eu-central-1.amazonaws.com' AWS_S3_ADDRESSING_STYLE = "virtual"

and also 1 additional: AWS_S3_REGION_NAME = 'eu-central-1'

[Jackevansevo]

Ran into this issue today and found both combinations work (for a public bucket)

AWS_S3_REGION_NAME = 'us-east-2'
AWS_S3_ENDPOINT_URL = f'https://s3.{AWS_S3_REGION_NAME}.amazonaws.com'

or

AWS_S3_REGION_NAME = 'us-east-2'
AWS_S3_ADDRESSING_STYLE = 'path'

along with my AWS_STORAGE_BUCKET_NAME