AWS_S3_ADDRESSING_STYLE = "virtual"
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.
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.
      
Based on current cookiecutter, with these changes:
 - No public buckets
 - Region eu-central-1, and virtual addressing, because of
   jschneier/django-storages#782 (comment)
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.
          
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'
          
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'
AWS_S3_REGION_NAME = 'us-east-2'
AWS_S3_ADDRESSING_STYLE = 'path'
along with my AWS_STORAGE_BUCKET_NAME
          
Thank you @Jackevansevo, I tried AWS_S3_ADDRESSING_STYLE = 'virtual' and I still would get the SignatureDoesNotMatch error but it works with AWS_S3_ADDRESSING_STYLE = 'path', my bucket is hosted in eu-west-3 .

It has the effect of changing the url from
https://{bucket_name}.s3.{region_name}.amazonaws.com
https://s3.{region_name}.amazonaws.com/{bucket_name}
If someone can tell me why this works and not the first url I would gladly appreciate.

EDIT: I waited one night and now both addressing style works, I literally spent all yesterday afternoon debugging this. RIP
          
Hi guys, I uploaded my application to Vercel and it started pointing out this error. However, when running the local application or in an EC2 instance, it generates another url with less information and I can access the file without problems.
Anyone else going through this that has resolved it?

My Region: us-east-1

My settings

AWS_S3_ACCESS_KEY_ID = os.environ.get("AWS_S3_ACCESS_KEY_ID")

AWS_S3_SECRET_ACCESS_KEY = os.environ.get("AWS_S3_SECRET_ACCESS_KEY")

AWS_STORAGE_BUCKET_NAME = os.environ.get("AWS_STORAGE_BUCKET_NAME")

AWS_S3_CUSTOM_DOMAIN = os.environ.get("AWS_S3_CUSTOM_DOMAIN")

AWS_STORAGE_PRIVATE_BUCKET_NAME = os.environ.get("AWS_STORAGE_PRIVATE_BUCKET_NAME")

AWS_DEFAULT_ACL = None

AWS_S3_SIGNATURE_VERSION = "s3v4"