S3 presigned URL upload fails with 'SignatureDoesNotMatch'
@devsingh05▲ 10 net votes
Common causes: the browser sends a different Content-Type than the one the URL was signed with (sign with ContentType and send exactly that header, or sign without it); the client was created for a different region than the bucket (set region_name to the bucket's region, and use signature_version='s3v4'); or the URL was modified (extra query params, re-encoding). Also check the clock: a skewed system clock makes signatures invalid. For browser uploads the bucket also needs a CORS rule allowing PUT from your origin.