TypeError: Object.defineProperty called on non-object in @aws-sdk/client-s3 v3.758.0

[eacet]

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

After updating @aws-sdk/client-s3 from 3.701.0 to 3.758.0, my AWS Lambda function started failing with the following error:

{
  "errorType": "TypeError",
  "errorMessage": "Object.defineProperty called on non-object",
  "trace": [
    "TypeError: Object.defineProperty called on non-object",
    "    at defineProperty (<anonymous>)",
    "    at __name (/var/task/src/functions/hello/handler.js:9789:37)",
    "    at <static_initializer> (/var/task/src/functions/hello/handler.js:9981:9)",
    "    at node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js (/var/task/src/functions/hello/handler.js:9976:34)",
    "    at __require (/var/task/src/functions/hello/handler.js:10:50)",
    "    at node_modules/@aws-sdk/client-s3/dist-cjs/index.js (/var/task/src/functions/hello/handler.js:21641:37)",
    "    at __require (/var/task/src/functions/hello/handler.js:10:50)",
    "    at Object.<anonymous> (/var/task/src/functions/hello/handler.js:31948:32)",
    "    at Module._compile (node:internal/modules/cjs/loader:1364:14)",
    "    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)"
  ]
}

Regression Issue

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

SDK version number

@aws-sdk/client-s3@3.758.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

18

Reproduction Steps

1. Install the latest version (3.758.0) of @aws-sdk/client-s3:

npm install @aws-sdk/client-s3@latest

2. Use the following Lambda function:

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

const s3 = new S3({ region: "us-east-1" });

export const handler = async (event: { key: string }) => {
  try {
    const bucketName = process.env.BUCKET_NAME;
    const objectKey = event.key;

    if (!bucketName || !objectKey) {
      throw new Error("Missing bucket name or object key");
    }

    const response = await s3.headObject({
      Bucket: bucketName,
      Key: objectKey,
    });

    return {
      statusCode: 200,
      body: JSON.stringify(response),
    };
  } catch (error: any) {
    return {
      statusCode: error.$metadata?.httpStatusCode || 500,
      body: JSON.stringify({ message: error.message }),
    };
  }
};

3. Deploy the Lambda function and invoke it with a test event:

{
  "key": "path/to/object.jpg"
}

4. The function fails with TypeError: Object.defineProperty called on non-object.

Observed Behavior

When executing a simple headObject call to S3 using @aws-sdk/client-s3@3.758.0, the function fails with a TypeError: Object.defineProperty called on non-object.

Full error log from Lambda execution logs:

2025-03-11T00:19:56.203Z	undefined	ERROR	Uncaught Exception 	{
    "errorType": "TypeError",
    "errorMessage": "Object.defineProperty called on non-object",
    "stack": [
        "TypeError: Object.defineProperty called on non-object",
        "    at defineProperty (<anonymous>)",
        "    at __name (/var/task/src/functions/hello/handler.js:9789:37)",
        "    at <static_initializer> (/var/task/src/functions/hello/handler.js:9981:9)",
        "    at node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js (/var/task/src/functions/hello/handler.js:9976:34)",
        "    at __require (/var/task/src/functions/hello/handler.js:10:50)",
        "    at node_modules/@aws-sdk/client-s3/dist-cjs/index.js (/var/task/src/functions/hello/handler.js:21641:37)",
        "    at __require (/var/task/src/functions/hello/handler.js:10:50)",
        "    at Object.<anonymous> (/var/task/src/functions/hello/handler.js:31948:32)",
        "    at Module._compile (node:internal/modules/cjs/loader:1364:14)",
        "    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)"
    ]
}

Expected Behavior

The function should successfully execute and return metadata from headObject, as it does in @aws-sdk/client-s3 version 3.701.0.

Possible Solution

Workaround

Downgrading to version 3.701.0 resolves the issue:

npm install @aws-sdk/client-s3@3.701.0

Additional Information/Context

No response

[renanwilliam]

same error here on node18

[kuhe]

Could you show the code block that threw the error? and what values were passed to Object.defineProperty?

[panamclipper707]

For me it errors at the init stage of the lambda function. It looks like some sort of update happened to some aws-sdk client libraries at some point that broke things. I solved by rolling back lambda runtime to (now deprecated) Node v16. As there were too many @aws-sdk/* libs that needed to be rolled back to previous versions to work on the node v18 runtime. I'm also using the NodejsFunction construct from the AWS CDK, so maybe I'm doing something wrong with the bundling options there.

[renanwilliam]

My workaround was exclude any @aws-sdk/* from build process and use from Lambda

[panamclipper707]

My workaround was exclude any @aws-sdk/* from build process and use from Lambda

I also got this to work using Node v22 runtime and by excluding @aws-sdk/* from the build process.

However I think this might be covering this issue up. When I log what version of @aws-sdk/client-s3 the current node v22 lambda runtime is using it is 3.726.1

It might be that the bugs were introduced in a later version, and that eventually a runtime update of the @AWS-SDK version used will cause these errors to appear even when using the included aws-sdk from the lambda runtime?

[kuhe]

When using a group of @aws-sdk and @smithy (also from AWS) packages, they sometimes need to be of a consistent mutually contemporary version group, that is, the versions that were published at the same time.

NPM package nesting usually works, but in cases like this I speculate that the issue may be caused by version disparities between certain clients and other core packages or clients.

Our recommended way to get multiple dependencies on the same track is like this, mentioned here.

{
  "name": "your-app",
  "dependencies": {
    "@aws-sdk/client-s3": "<=3.768.0",
    "@aws-sdk/client-dynamodb": "<=3.768.0",
    "@aws-sdk/client-lambda": "<=3.768.0",
  }
}

---

That aside, could you make a small reproduction repository including a package-lock.json or equivalent lockfile to reproduce this issue in a plain Node.js runtime? It may be something that happens for a very specific combination of packages.

[balazs4]

👋 we were facing a very similar issue once we tried to upgrade aws-sdk version.
please note we tested it with DynamoDB instead of S3, but hence the error message is the same, it might help for further investigation.

We are able to create a very minimal environment, where we only add packages which causes the problem.

Setup:

node -v
v20.15.1

// index.js
require("@aws-sdk/lib-dynamodb");
console.log("hello");

{
  "name": "aws-def-props",
  "scripts": {
    "build": "esbuild index.js --bundle --platform=node > dist.js",
    "start": "node dist.js"
  },
  "dependencies": {
    "@aws-sdk/lib-dynamodb": "3.624.0"
  },
  "devDependencies": {
    "esbuild": "0.17.19"
  }
}

> node dist.js

hello

It works expected 👍

However, once we upgraded the @aws-sdk/lib-dynamodb

{
  "name": "aws-def-props",
  "scripts": {
    "build": "esbuild index.js --bundle --platform=node > dist.js",
    "start": "node dist.js"
  },
  "dependencies": {
-    "@aws-sdk/lib-dynamodb": "3.624.0"
+    "@aws-sdk/lib-dynamodb": "3.775.0"
  },
  "devDependencies": {
    "esbuild": "0.17.19"
  }
}

we got the following error (same as OP)

> node dist.js

/Users/balazs4/src/aws-def-props/dist.js:23959
    var __name = (target, value) => __defProp2(target, "name", { value, configurable: true });
                                    ^

TypeError: Object.defineProperty called on non-object
    at defineProperty (<anonymous>)
    at __name (/Users/balazs4/src/aws-def-props/dist.js:23959:37)
    at <static_initializer> (/Users/balazs4/src/aws-def-props/dist.js:24085:9)
    at node_modules/@aws-sdk/lib-dynamodb/dist-cjs/index.js (/Users/balazs4/src/aws-def-props/dist.js:24083:85)
    at __require (/Users/balazs4/src/aws-def-props/dist.js:12:50)
    at Object.<anonymous> (/Users/balazs4/src/aws-def-props/dist.js:24922:1)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)

Node.js v20.15.1

Updating the esbuild version as well

{
  "name": "aws-def-props",
  "scripts": {
    "build": "esbuild index.js --bundle --platform=node > dist.js",
    "start": "node dist.js"
  },
  "dependencies": {
-    "@aws-sdk/lib-dynamodb": "3.624.0"
+    "@aws-sdk/lib-dynamodb": "3.775.0"
  },
  "devDependencies": {
-    "esbuild": "0.17.19"
+    "esbuild": "0.18.20"
  }
}

> node dist.js

hello

fixed our issue and it worked again as expected.

cc @vvo

[kuhe]

@balazs4 what is the code at and surrounding this line?

at __name (/Users/balazs4/src/aws-def-props/dist.js:23959:37)

The __name function is a local esbuild helper function that assigns canonical names to functions.