S3 PutObjectCommand does not require the property `Body`, hangs request when no body is passed.

[prenaissance]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

The type PutObjectCommandInput, passed as an argument to the constructor of PutObjectCommand, does not require the Body property. Sending the command makes the connection hang and eventually timeout.

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-s3@3.779.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v22.14.0

Reproduction Steps

const s3 = new S3Client(myOptions);
const s3Response = await s3.send(
   new PutObjectCommand({
     Bucket: 'some-bucket',
     Key: 'some-key',
     ContentType: 'application/zip',
   }),
); // this will hang and eventually timeout

Observed Behavior

Slightly edited error log message:

err: {
  "type": "Error",
  "message": "{\"path\":\"/program/welcome-letter-batch/d54cbc88-aae3-41a2-8d3a-0c35f2e2b111\",\"message\":\"Internal Server Error\"}",
  "stack":
      Error: Attribute 'lang' is without value.:2:7
        Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.
          at XMLParser.parse ([my-path]/node_modules/fast-xml-parser/src/xmlparser/XMLParser.js:30:21)
          at [my-path]/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:177:26
          at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
          at async parseXmlErrorBody ([my-path]/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:198:17)
          at async de_CommandError ([my-path]/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4907:11)
          at async [my-path]/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
          at async [my-path]/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:484:18
          at async [my-path]/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
          at async [my-path]/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:318:18
          at async [my-path]/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:110:22
          at async [my-path]/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:137:14
          at async [my-path]/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22
          ... project files
          at async [my-path]/node_modules/@nestjs/core/router/router-execution-context.js:46:28
}

Expected Behavior

I'm not sure why undefined is allowed as the value for the Body parameter, but if it is allowed I'd expect an empty object to be created.

Possible Solution

No response

Additional Information/Context

OS: MacOS 15.3.1
Architecture: ARM64 Apple Silicon
Using NestJS 11 and pino, which might have interfered with the error message. I'll try to get a sandboxed reproduction later.

[zshzbh]

Hey @prenaissance ,

It seems that you ran the code in NextJS 11 instead of node.js, right?

I tried on node.js since you mentioned this issue happened in node.js -

Which JavaScript Runtime is this issue in?
Node.js

and I don't see the issue. I got a 200 response.

The code I have -

import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";
const s3 = new S3Client({region: "us-east-1"});
const s3Response = await s3.send(
   new PutObjectCommand({
     Bucket: 'new-bucket-maggie-ma',
     Key: 'some-key',
     ContentType: 'application/zip',
   }),
); // this will hang and eventually timeout
console.log(s3Response)

It seems that in your code, you missed a ' in Key: 'some-key;,, could you please check your code and see if you also missed the ' in your actual project? If so, could you please fix this line and see if the err still exists?

If the issue I mentioned doesn't exist in your code or it's fixed but the error still exists - It seems that there's a Deserialization error:, could you please log {error}.$response ?

Thanks!~

[prenaissance]

Sorry for the delayed response.

And sorry for the typo, but that was not the issue. I could not replicate this on a sandboxed environment. At work I added some logic to avoid this scenario. I'll close the issue and reopen it if I get the replication steps.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[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.