Lambda handlers should be upgraded to Node.js 18

[echeung-amzn]

Version

v5.2.3

Steps and/or minimal code example to reproduce

1. Use bitmap widgets or secrets monitoring

Expected behavior

Have Lambda functions deployed that aren't using an EOL version of Node.js.

Actual behavior

Functions are using Node.js 14.

Other details

Relevant functions:

• https://github.com/cdklabs/cdk-monitoring-constructs/blob/81f0c6ba0211bca586c9b994ec7aa037b2cd6e3c/lib/dashboard/widget/BitmapWidget.ts#L37
• https://github.com/cdklabs/cdk-monitoring-constructs/blob/81f0c6ba0211bca586c9b994ec7aa037b2cd6e3c/lib/monitoring/aws-secretsmanager/SecretsManagerMetricsPublisher.ts#L37

The actual handlers need to be updated to use aws-sdk v3 and/or bundled code.

[echeung-amzn]

We are ending support for Node.js 14 in AWS Lambda. This follows Node.js 14 End-Of-Life (EOL) reached on April 30, 2023 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 27, 2023, Lambda will no longer apply security patches and other updates to the Node.js 14 runtime used by Lambda functions, and functions using Node.js 14 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 14 runtime. Starting January 25, 2024, you will no longer be able to update existing functions using the Node.js 14 runtime.

We recommend that you upgrade your existing Node.js 14 functions to Node.js 18 before November 27, 2023.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.