The request signature we calculated does not match the signature you provided. Check your key and signing method. about react-s3-uploader HOT 5 OPEN

If you select the bucket and go to Properties > Permissions > Edit CORS Configuration, add something like

</CORSConfiguration>
    <CORSRule>
        <AllowedOrigin>Your-Base-Domain-Here</AllowedOrigin>
        <AllowedMethod>PUT</AllowedMethod>
        <AllowedHeader>*</AllowedHeader>
    </CORSRule>
</CORSConfiguration>

from react-s3-uploader.

Thanks @dgrosenblatt, however that didn't turn out to be my issue.

After futzing around for a while I ended up creating a new user with the exact same policy and voila, 🍾 .

Here's the policy for reference:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:PutObjectAcl"
            ],
            "Resource": "arn:aws:s3:::bucket_name/*"
        }
    ]
}

from react-s3-uploader.

Can you verify that your AWS credentials are correctly configured in Node? For example, are you able to make any other requests to any AWS service?

from react-s3-uploader.

I got a very similar looking error message, and it was due to the CORS policy on my AWS bucket. This might be the case if you can use curl to successfully upload to the presigned url that your server is generating.

from react-s3-uploader.

@dgrosenblatt For the rest of us, what was the problem with your CORS config in AWS? What did you do to fix it?

from react-s3-uploader.