📊Tracking: upgrade to Node 20

[evgenyka]

Overview

Node 18, which is currently in its Active LTS phase, is slated to reach its End of Life on 2025-04-30, as indicated on https://nodejs.dev/en/about/releases/.
Our aim is to provide CDK users with sufficient preparation time for the transition to the latest LTS Node version - Node 20. CDK plan to carry out the Node version upgrade by 2024-10-30, which is six months prior to the End of Life date.

Link to the service’s CDK Construct Library API reference page.

N/A

Maturity: CloudFormation Resources Only

Stable

Implementation

TBD

Issue list

• aws-cdk-lib: NODEJS_LATEST still points to nodejs18.x  #28125
• [ ]

[estrudels]

Update around preview of AWS Lambda (Node 20 Support)

• Node v20 Released aws-lambda-base-images#91 (comment)
• https://docs.aws.amazon.com/linux/al2023/ug/minimal-container.html

[haata]

Any progress? Slated completion is less than 2 weeks away.

[QuantumNeuralCoder]

There are 2 issues in consideration here.

1. CDK Custom resources using NodeJs as managed runtime for Lambda function. Customers cannot change or override the nodejs version for these custom resources. To mitigate this CDK released a region-awareness feature in v2.146.0 on 6/13. Due to this feature, the custom resources will use the lambda managed runtime available in your region. You should be able to see nodejs20 being used in commercial regions.

• implement node runtime region awareness for cdk vended custom resources (#30108) (69c5dde)

2. Variable nodejs_latest in (aws-cdk-lib/aws-lambda/lib/runtime.js). Customers can use the nodejs version of their choice instead of depending on this variable. This will be upgraded as we work on resolving a lambda runtime support dependency. Lambda runtime support timelines for the nodejs versions can be found in this doc