SignatureDoesNotMatch while uploading an object to S3 with ContentType

[Tietew]

Describe the bug
SignatureDoesNotMatch occures while uploading an object to S3 with ContentType.

SDK version number
@aws-sdk/[email protected]

Is the issue in the browser/Node.js/ReactNative?
Node.js

Details of the browser/Node.js/ReactNative version

$ node -v
v12.20.0

To Reproduce (observed behavior)

Run following script

import { S3 } from '@aws-sdk/client-s3';

const s3 = new S3({ region: 'ap-northeast-1' });
s3.putObject({
  Bucket: 'mybucketname',
  Key: 'blah.json',
  ContentType: 'application/json',
  Body: Buffer.from(JSON.stringify({ dead: 'beef' })),
}).then(console.log, console.error);

Got

SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

Expected behavior
An object s3://mybucketname/blah.json is created with its Content-Type is application/json.

Additional context
With no ContentType, object is successfully created but its Content-Type is application/octet-stream.

[joain946]

I just ran into this issue as well.
The problems seems to be that there are two content type headers being added. The one specified in PutObject ends up as "Content-Type" then the other header that is being added behind the scene is added as "content-type".
The only workaround I have found so far is to create your own "signer" object when creating the S3 client and that class can then filter out the "content-type" header and then delegate to the "SignatureV4.ts" class.

Here is what the headers for the signing looks like when getting into the SignatureV4.sign(...) method:

[AllanZhengYP]

Hi @Tietew @joain946

I can confirm this is a bug. We will fix it soon. Thanks a lot for reporting and investigating in this.

[apostolos]

Adding "content-type": true in ALWAYS_UNSIGNABLE_HEADERS seems to fix the problem:
https://github.com/aws/aws-sdk-js-v3/blob/master/packages/signature-v4/src/constants.ts#L18-L34

[adamdottv]

Hi @Tietew @joain946

I can confirm this is a bug. We will fix it soon. Thanks a lot for reporting and investigating in this.

Hi @AllanZhengYP, any chance you have an ETA on this fix? Or are there any known workarounds?

[adamdottv]

I'm actually working around it with middleware until this is fixed; in case this is helpful to anyone else:

const s3 = new S3()

s3.middlewareStack.add(
  (next) => async (args) => {
    delete args.request.headers['content-type']
    return next(args)
  },
  {step: 'build'},
)

await s3.putObject({
  Bucket: bucket,
  Key: key,
  Body: body,
  ContentType: contentType,
})

[xeaone]

Maybe this is assumed but I wanted to add that this issue also plagues the v3 modular interface. Also @adamelmore middleware workaround gets past the issue for the modular interface.

[gswebspace]

Ran into this as well. Adding ContentType results in SignatureDoesNotMatch.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.