Receiving "SignatureDoesNotMatch" errors when using Spaces with Postman

Posted September 24, 2017 11.7k views
APIObject Storage

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>

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

  • It’s seams like DO spaces it’s not very ready for production use. They say that supported only V2 signature version, but signing with V2 also does not work.

  • Hi there - I’m the product manager for Spaces. Thanks for letting us know that you ran into an issue.

    Would you be able to try again with a new access/secret key OR by regenerating an existing key?

    We in the last few days changed how key regeneration is done (we now regenerate the access key AND the secret) and using a new keypair (or regenerating an existing one again) is the likely fix for what you’ve reported.

    If for some reason that doesn’t work, please let us know.

  • I’ve tried again with a new access/secret, but sadly still getting the same result. Has anyone managed to use ‘put’ with spaces via postman to create a new file?

  • Hello there,

    I’m getting the same error via Transmit 5.

    @johngannon any idea when this may be solved? thanks

  • @antoniorosado Transmit just released v.5.0.5 which has a fix/fixes that allow it to work well with Spaces. Hope this helps.

  • Show 4 more comments

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.

Submit an Answer
10 answers

i got it working like this:

For: get

in the postman tab authorization :
Type: AWS Signature
AccessKey : <KEY HERE>
SecretKey : <KEY HERE>
AWS Region : ams3
Service Name : s3
Session Token : myTok

edited by MattIPv4

Auth fails with this error when the ‘x-amz-content-sha256’ header value is not set, might be relevant

Facing same issue using SociallyDev Spaces-API

This still seems to be an issue.

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' : '',
    '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
edited by asb

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


Same probleam with Postman

I got it to work in Postman version 7.36.1

In the Authorization tab, I selected “AWS Signature” as the type and filled out the following:
Access Key : [ my key ]
Secret Key : [ my secret ]
AWS Region : nyc3 (or whatever Digital Ocean region you’re using)
Service Name : s3
Session Token : [leave blank]

It seems by default SDK/Library uses signature v2 which does not support by the digital ocean.

Try overriding to v4

const s3 = new AWS.S3({
      accessKeyId: key,
      secretAccessKey: secret,
      endpoint: spacesEndpoint,
      region: 'sgp1',
      signatureVersion: 'v4',

take a look at the AWS_S3_ENDPOINT_URL it must be some thing like: ''