Report this

What is the reason for this report?

Receiving "SignatureDoesNotMatch" errors when using Spaces with Postman

Posted on September 24, 2017

Very similar to the other ‘SignatureDoesNotMatch’ question but having issues with Postman,

So i’m trying to use postman to gain access to my files. I’ve set up the ‘AccessKey’ and ‘SecretKey’ pair within the API section in digital ocean but constantly getting ‘<Error> <Code>SignatureDoesNotMatch</Code>…’

anyone had any luck working through postman to access object spaces?



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.

Same probleam with Postman

Was this resolved in the end please? I am using Transmit 5 and getting the SignatureDoesNotMatch error. Can see my bucket though.

Thanks

Following Node.JS code is working for me. I suspect, we need to set up minimum 4 connection parameters.

*var AWS = require('aws-sdk');
exports.getBuckets = async function(req, res) 
{
  var options = {
    'endpoint' : 'https://nyc3.digitaloceanspaces.com',
    'accessKeyId' : 'XXXX',
    'secretAccessKey' : 'YYY,
    'region' : 'nyc3'
  };
  var s3 = new AWS.S3(options);
  s3.listBuckets(function(err, data) {
    if (err) console.log(err, err.stack); // an error occurred
    else     console.log(data);           // successful response
  });
};*

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.