403 error with version 1.6.3 of boto3

django version: 2.0.2 django-s3-storage version: 0.12.4 boto3 version: 1.6.3

Uploading a file then accessing the url results in a 403 error with the message:

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

Last version of boto3 I used that made django-s3-storage work was 1.5.2. This time version 1.6.3 autoinstalled as a dep and it threw the above error.

As always, thank you for such a wonderful module.

[wesleykendall]

@etianen and others, I had this error until I found this https://github.com/boto/boto3/issues/1644#issuecomment-434566036

To get rid of this error, set the following settings:

AWS_S3_ADDRESSING_STYLE = 'path'

Now I successfully can view objects with boto3=1.14.45 and django-s3-storage=“0.13.3”

@etianen do you think this should be changed to the default setting? I’m happy to open a PR. A better solution might be adjusting this based on the boto3 version, but I’m not sure if I will have time to make that PR

[tomwojcik]

I struggled with lots of errors but finally managed to make it work (for generate_presigned_post).

I get my client from (if you need it)

client = S3Boto3Storage().bucket.meta.client

And those are the settings you need to experiment with

AWS_S3_SIGNATURE_VERSION = "s3v4"  # required for some regions
AWS_S3_ADDRESSING_STYLE = 'path'  # needed only in some cases, depending on your boto3 version
AWS_S3_REGION_NAME = ...  # might be necessary if your region is non-default

boto3==1.18.4
django-storages==1.11.1