Skip to content

The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256 when using region Frankfurt #5002

Description

@jurajpetrik

When I create a bucket on AWS with the region:Frankfurt there will be an error on connecting.

Furthermore, the error message isn't very helpful.

 events.js:74
         throw TypeError('Uncaught, unspecified "error" event.');
               ^
 TypeError: Uncaught, unspecified "error" event.
     at TypeError (<anonymous>)
     at Writable.EventEmitter.emit (events.js:74:15)
     at /home/juraj/code/sportlookbackend/node_modules/skipper-s3/index.js:238:22
     at PassThrough.MultiPartUpload._handleStream      (/home/juraj/code/sportlookbackend/node_modules/skipper-s3/node_modules/knox-mpu-     alt/lib/multipartupload.js:328:16)
     at PassThrough.EventEmitter.emit (events.js:117:20)
     at module.exports           (/home/juraj/code/sportlookbackend/node_modules/sails/node_modules/skipper/standalone/Upstream/     prototype.fatalIncomingError.js:65:17)
     at Function.forEach           (/home/juraj/code/sportlookbackend/node_modules/sails/node_modules/lodash/dist/lodash.js:3297:15)
     at lodash.ctor.(anonymous function) [as each]      (/home/juraj/code/sportlookbackend/node_modules/sails/node_modules/lodash/dist/lodash.js:5924:31)
     at Upstream.fatalIncomingError      (/home/juraj/code/sportlookbackend/node_modules/sails/node_modules/skipper/standalone/Upstream/     prototype.fatalIncomingError.js:55:18)
     at Writable.unableToUpload      (/home/juraj/code/sportlookbackend/node_modules/sails/node_modules/skipper/standalone/Upstream/     prototype.upload.js:142:10)
     at Writable.g (events.js:180:16)
     at Writable.EventEmitter.emit (events.js:117:20)
     at /home/juraj/code/sportlookbackend/node_modules/skipper-s3/index.js:238:22
     at MultiPartUpload._putStream (/home/juraj/code/sportlookbackend/node_modules/skipper-     s3/node_modules/knox-mpu-alt/lib/multipartupload.js:217:42)
     at MultiPartUpload._initiate (/home/juraj/code/sportlookbackend/node_modules/skipper-     s3/node_modules/knox-mpu-alt/lib/multipartupload.js:131:18)
     at Parser.exports.Parser.Parser.parseString      (/home/juraj/code/sportlookbackend/node_modules/skipper-s3/node_modules/knox-mpu-     alt/node_modules/xml2js/lib/xml2js.js:255:20)

Luckily it's just a case of skipper not passing the error message through. When I put a breakpoint in

node_modules/sails/node_modules/skipper/standalone/Upstream/prototype.fatalIncomingError.js:55

I can see the error. It is the following:

    "Unable to initiate stream upload [Error: Unexpected response from AWS:{ Code: 'InvalidRequest',
     Message: 'The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.',

And it can be tracked down to a known issue in knox that skipper-s3 uses for AWS communication.
Automattic/knox#254

And they already seem to be working on a fix for that Automattic/knox#273

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions