s3: Custom s3 auto delete lambda is still using node 20.x

[yaseen104]

Describe the bug

After 2.168.0 there was a support for node 22.x.
Below is the code
const s3BucketWeb = new s3.Bucket(stack,${envProps.environmentName}-s3-web, { // Block all public access blockPublicAccess: s3.BlockPublicAccess.BLOCK_ALL, // When stack is deleted, delete this bucket also removalPolicy: cdk.RemovalPolicy.DESTROY, // Delete contained objects when bucket is deleted autoDeleteObjects: true });

But the CustomS3AutoDelete Lambda is till taking the node 20.x
Tried the version till 2.180.0.

Regression Issue

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

Last Known Working CDK Version

No response

Expected Behavior

The node version should be updated to 22.

Current Behavior

It is still taking node 20

Reproduction Steps

const s3BucketWeb = new s3.Bucket(stack,${envProps.environmentName}-s3-web, { // Block all public access blockPublicAccess: s3.BlockPublicAccess.BLOCK_ALL, // When stack is deleted, delete this bucket also removalPolicy: cdk.RemovalPolicy.DESTROY, // Delete contained objects when bucket is deleted autoDeleteObjects: true });

Using this code, this will create the auto delete objects

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.170.0

Framework Version

No response

Node.js Version

20

OS

windows

Language

TypeScript

Language Version

No response

Other information

No response

[pahud]

Hi @yaseen104,

Thank you for reporting this issue. You're correct that the CustomS3AutoDelete Lambda function is still using Node.js 20.x despite Node.js 22.x being a supported runtime in AWS CDK since version 2.168.0.

After investigating, I can explain why this is happening:

1. The S3 bucket's autoDeleteObjects: true option creates a custom resource that uses the AutoDeleteObjectsProvider class. This provider determines which Node.js runtime to use by calling a function named determineLatestNodeRuntimeName.

2. This function checks the CDK's regional fact database (in fact-tables.ts) to determine the latest available Node.js runtime for the deployment region. Looking at this file, I can see that the current mapping specifies:

aws-cdk/packages/aws-cdk-lib/region-info/build-tools/fact-tables.ts

Lines 111 to 119 in f44209e

	export const LATEST_NODE_RUNTIME_MAP: Record<Partition, string> = {
	[Partition.Default]: Runtime.NODE_20,
	[Partition.Cn]: Runtime.NODE_20,
	[Partition.UsGov]: Runtime.NODE_20,
	[Partition.UsIso]: Runtime.NODE_18,
	[Partition.UsIsoB]: Runtime.NODE_18,
	[Partition.UsIsoF]: Runtime.NODE_18,
	[Partition.EuIsoE]: Runtime.NODE_18,
	};

3. The current approach is to only update the "latest" runtime designation when a runtime is available in all AWS regions, including specialized ones like GovCloud and China regions.

This behavior is by design rather than a bug. AWS CDK is being cautious about updating the "latest" runtime designation to ensure consistent behavior across all regions. Once Node.js 22.x becomes available in all regions, the CDK team will likely update the LATEST_NODE_RUNTIME_MAP to use it.

I'll bring this issue up to the team to review and re-evaluate if it's OK to bump the latest to node22.

[pahud]

related to #27003 (comment)

[SimonCMoore]

As Pahud says and is as intended and tracked in #27003 we are currently using Node 20 in commercial regions for custom resources. For lambdas you author you can use NODEJS_22_X \for the runtime. I will close this in favour of the tracking issue.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.