[S3 Client] Errors if the `Body` of `PutObjectCommand` is a `Readable` type.

Describe the bug

I got this error when I set the Body to a Readable type.

(node:88634) UnhandledPromiseRejectionWarning: NotImplemented: A header you provided implies functionality that is not implemented

SDK version number 3.13.1

To Reproduce (observed behavior)

import { fromIni } from '@aws-sdk/credential-provider-ini'
import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3'
import https from 'https'
import { Readable } from 'stream'
import awsConfig from './aws-exports'

const s3Client = new S3Client({
  credentials: fromIni({ profile: 'default' }),
  region: 'ap-northeast-1',
})

async function getFileFromUrl(url: string): Promise<Readable> {
  return new Promise((resolve) => {
    https.get(url, (response) => {
      resolve(response)
    })
  })
}

async function upload(file: Readable) {
  const uploadCommand = new PutObjectCommand({
    Bucket: awsConfig.aws_user_files_s3_bucket,
    Key: 'test.jpg',
    Body: file,
    ACL: 'public-read',
  })

  await s3Client.send(uploadCommand)
}

async function migrate() {
  const file = await getFileFromUrl(
    'https://example.com/logo.png'
  )
  await upload(file)
  console.log('done')
}

migrate()

I could confirm that it’s ok if I change the Body to a string, so I’m sure I have the right permission to put an object to the bucket.

[ffxsam]

Just in case anyone needs a clear answer: putObject can’t write a stream to S3, you have to use the Upload class in @aws-sdk/lib-storage.

[AllanZhengYP]

Hi @fabis94 @yaquawa @guanzo, The error is indeed caused by stream length remaining unknown. We need to improve the error message and the documentation. As it’s pointed out in the Upgrading Guide, the similar functionality as s3.upload() in v2 is now moved to @aws-sdk/lib-storage package.