NodejsFunction: Inconsistent SDK behavior with and without runtime specification

[rupe120]

Describe the bug

The bundled SDK is different when a runtime is specified, as opposed to when it is left as default.

Expected Behavior

The behavior of the SDK when using the default runtime value is the expected behavior.

Current Behavior

If you try to use newer methods, like the QuickSight asset export methods an error saying that the classes are not constructors.

The following is what is produced when specifying runtime: lambda.Runtime.NODEJS_18_X

{
  "errorType": "TypeError",
  "errorMessage": "import_client_quicksight.StartAssetBundleExportJobCommand is not a constructor",
  "trace": [
    "TypeError: import_client_quicksight.StartAssetBundleExportJobCommand is not a constructor",
    "    at startQuicksightAssetExport (/var/task/index.js:47:30)",
    "    at Runtime.handler (/var/task/index.js:71:40)",
    "    at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1083:29)"
  ]
}

The following is what the same line produces without specifying a runtime value

{
  "errorType": "ValidationException",
  "errorMessage": "1 validation error detected: Value '[]' at 'resourceArns' failed to satisfy constraint: Member must have length greater than or equal to 1",
  "trace": [
    "ValidationException: 1 validation error detected: Value '[]' at 'resourceArns' failed to satisfy constraint: Member must have length greater than or equal to 1",
    "    at throwDefaultError (/var/task/index.js:9134:24)",
    "    at /var/task/index.js:9144:39",
    "    at de_StartAssetBundleExportJobCommandError (/var/task/index.js:30731:18)",
    "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
    "    at async /var/task/index.js:6077:24",
    "    at async /var/task/index.js:3722:22",
    "    at async /var/task/index.js:7329:42",
    "    at async /var/task/index.js:1186:26",
    "    at async startQuicksightAssetExport (/var/task/index.js:48531:41)",
    "    at async Runtime.handler (/var/task/index.js:48554:34)"
  ]
}

Each of these produce a Lambda using the NodeJs 18 runtime.

Reproduction Steps

Deploy the following repo into an account and run the quicksight-start-asset-export-w-runtime and quicksight-start-asset-export Lambdas.

https://github.com/rupe120/cdk-typescript-quicksight-sdk-test

Possible Solution

Unknown

Additional Information/Context

No response

CDK CLI Version

2.88.0

Framework Version

No response

Node.js Version

v18.16.1

OS

Windows 11 Enterprise build 22621.1702

Language

Typescript

Language Version

Typescript 5.1.6

Other information

No response

[pahud]

I guess it's because the default runtime is node14 which does not come with SDK v3 yet provided in node18.

aws-cdk/packages/aws-cdk-lib/aws-lambda-nodejs/lib/function.ts

Lines 39 to 41 in 1b36124

	* @default Runtime.NODEJS_14_X
	*/
	readonly runtime?: lambda.Runtime;

And according to this, node18 runtime comes with SDK version 3.188.0 at this moment. If you need new methods that only available after 3.188.0 you probably have to bundle the latest aws js sdk into your lambda function with externals or nodeModules.

[peterwoodworth]

Yes exactly @pahud, I think this is expected given the Lambda runtime defaults.

[rupe120]

Except they were both generated with NodeJs 18, and it's the one that I did not select NodeJs 18 explicitly and used the default behavior where the newer SDK call did work.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.