Question
"Signature Does Not Match" when putting to presigned spaces upload url
- Posted on October 24, 2017
- DigitalOceanJavaScriptNode.js
Asked by Sam Johnson
I am using the aws-sdk in Node.js to generate a presigned putObject upload url for use with DigitalOcean Spaces. The url gets generated just fine, however when I try putting to it using a REST client, I get a SignatureDoesNotMatch error. Below is the code I am using to generate the presigned url (from within a Google Cloud Function):
var AWS = require('aws-sdk');
AWS.config.loadFromPath('./credentials.json');
var s3 = new AWS.S3({params: {Bucket: 'bucket-name'}});
exports.requestUploadUrl = function requestUploadUrl(req, res) {
var key = 'some-predefined-key';
s3.getSignedUrl('putObject', {Bucket: 'bucket-name', Key: key}, function (err, url) {
res.send(url);
});
}
I am getting this sort of response when I try posting to the presigned url:
<?xml version="1.0" encoding="UTF-8" ?>
<Error>
<Code>SignatureDoesNotMatch</Code>
<RequestId>tx000000000000000664ed3-0059eeef91-3777b-nyc3a</RequestId>
<HostId>3777b-nyc3a-nyc</HostId>
</Error>
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
So the reason this wasn’t working is the content type MUST be specified when generating the presigned URL and specified once again by the client when it connects, and they must exactly match. Once I specified application/octet-stream everything worked
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Its sad that AWS give wrong examples in its documentation. When i first tried python example even the signing key creation method was faulty. For your problem i would suggest you replicate their Requests even use same AccessKeyId and secretacesskey as given in examples. Then compare the signature and payload hash. If it doesn’t match than start debugging. 2- I think aws multipart request doesn’t work with presigned urls with REST. Either you have to use AWS SDK or use Authorization Header.
Thanks Sahil DESWAL Creator of bluntfox.com
@anoopg your problem is a bit more simple. The
accessKeyIdis the name you gave your spaces access key, and thesecretAccessKeyis simply the value of the key. You don’t need to use a personal access token at all for this.I am also facing the same issue. I need a clarification here, what is the secrete key here ? I am taking keys generated in Personal access tokens as secret key and Spaces access keys as access key id. AWS.config.update({ “accessKeyId”: Spaces access keys, “secretAccessKey”: Personal access tokens });
Can you please clarify if I am considering accessKeyId and secretAccessKey properly ?