Maintenance: End Of Support of Node.js 12 runtime

[saragerion]

Note
AWS Lambda has updated the table of Supported Runtimes to reflect that the deprecation has been delayed to Mar 31, 2023.

---

Description of the feature request

Problem statement

AWS is ending support for Node.js 12 in AWS Lambda. This follows Node.js 12 End-Of-Life (EOL) reached on April 30, 2022.
Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, customers will no longer be able to create new Lambda functions using the Node.js 12 runtime.
Starting December 14, 2022, customers will no longer be able to update existing functions using the Node.js 12 runtime.

Summary of the feature

Remove support and references of Node.js 12 included but not limited to:

• CI/CD pipelines
• Documentation (readme, docs)
• Examples

Code examples

Benefits for you and the wider AWS community

Migration to the latest stable Node.js runtime with improved performance and new features.

Describe alternatives you've considered

N/A

Additional context

AWS recommends that customers upgrade their existing Node.js 12 functions to Node.js 16 before November 14, 2022.
End of support does not impact function execution. Customer's 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.

The following command shows how to use the AWS CLI to list all functions in a specific region using Node.js 12. To find all such functions in an AWS account, customers can repeat this command for each region:

aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='nodejs12.x'].FunctionArn"

For more information, refer to the AWS Lambda runtime deprecation policy.

Related issues, RFCs

N/A

[saragerion]

IMPORTANT: this unit of work should be released only after the deprecation takes place for customers, so after December 14, 2022.

[ijemmy]

Note for implementer. Please check if we can also update the target from ES2019 to a newer version. It was implemented in this PR: #925

[dreamorosi]

I think we should instead drop support at the latest on November 14 (a month before) & indicate the last release before then as the last supporting NodeJS 12. In the messaging shared via email (& that you copied above) it says that after this date it worn't be possible to create new functions using the runtime. This means we won't be able to run e2e tests after that date.

In theory we could modify our e2e tests to reuse an existing Lambda function instead of creating a new one, but personally I don't think it's worth the effort.

As additional data points:

• The AWS SDK v3 for NodeJS will deprecate the runtime a month and half before that (1 November) - link.
• Depending on where we stand with the upcoming utilities (Idempotency & Parameters), if we were tu support NodeJS 12 for longer, we'd be doing so without official support of the main dependency (aws-sdk).

My vote would be to align with the AWS SDK v3 timeline instead.

[dreamorosi]

Deprecation date has been postponed to Mar 31, 2023 so we can put this task on hold.

I have updated the issue body to reflect the change. We'll revisit this later on.

[dreamorosi]

CDK has marked the runtime as deprecated (2.43.0): aws/aws-cdk@b8c2abf

Jest has dropped support for Node 12 with 29.x: https://github.com/facebook/jest/releases/tag/v29.0.0-alpha.0