Prerequisites
Steps to Reproduce
Expected Behavior
Actual Behavior
PyRun Version (if known)
No response
Browser & Operating System
n/a
Workspace & Runtime Details
Some pyrun internal functions are using node.js 20.x.
EOL is April 30, 2026.
We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the Node.js 20.x runtime.
We are ending support for Node.js 20.x in Lambda on April 30, 2026. This follows Node.js 20.x End-Of-Life (EOL) scheduled on April 30, 2026 [1]. 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.
As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages.
-
Starting on April 30, 2026, Lambda will no longer apply security patches and other updates to the Node.js 20.x runtime used by Lambda functions, and functions using Node.js 20.x will no longer be eligible for technical support. Also, Node.js 20.x will no longer be available in the AWS Console, although you can still create and update functions using Node.js 20.x via AWS CloudFormation, the AWS CLI, AWS Serverless Application Model (SAM), or other tools.
-
Starting June 1, 2026, you will no longer be able to create new Lambda functions using the Node.js 20.x runtime.
-
Starting July 1, 2026, you will no longer be able to update existing functions using the Node.js 20.x runtime.
We recommend that you upgrade your existing Node.js 20.x functions to the latest available Node.js runtime in Lambda before April 30, 2026.
Your impacted Lambda functions using the Node.js 20.x runtime are listed on the 'Affected resources' tab of your AWS Health Dashboard.
This notification is generated for functions using the Node.js 20.x runtime for the $LATEST function version. The following command shows how to use the AWS CLI [3] to list all functions in a specific region that is using Node.js 20.x, including published function versions. To find all such functions in your account, repeat the following command for each region:
aws lambda list-functions --region us-east-1 --output text --query "Functions[?Runtime=='nodejs20.x'].FunctionArn"
Starting 180 days before deprecation, you can also use Trusted Advisor to identify functions using the Node.js 20.x runtime [4].
If you have any concerns or require further assistance, please contact AWS Support [5].
Runtime deprecation may occasionally be deferred for operational reasons. You can check active notifications in AWS Health and the Lambda runtime documentation [6] for the current schedule.
Relevant Logs
Additional Context (Screenshots, etc.)
No response
Prerequisites
Steps to Reproduce
Expected Behavior
Actual Behavior
PyRun Version (if known)
No response
Browser & Operating System
n/a
Workspace & Runtime Details
Some pyrun internal functions are using node.js 20.x.
EOL is April 30, 2026.
We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the Node.js 20.x runtime.
We are ending support for Node.js 20.x in Lambda on April 30, 2026. This follows Node.js 20.x End-Of-Life (EOL) scheduled on April 30, 2026 [1]. 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.
As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages.
Starting on April 30, 2026, Lambda will no longer apply security patches and other updates to the Node.js 20.x runtime used by Lambda functions, and functions using Node.js 20.x will no longer be eligible for technical support. Also, Node.js 20.x will no longer be available in the AWS Console, although you can still create and update functions using Node.js 20.x via AWS CloudFormation, the AWS CLI, AWS Serverless Application Model (SAM), or other tools.
Starting June 1, 2026, you will no longer be able to create new Lambda functions using the Node.js 20.x runtime.
Starting July 1, 2026, you will no longer be able to update existing functions using the Node.js 20.x runtime.
We recommend that you upgrade your existing Node.js 20.x functions to the latest available Node.js runtime in Lambda before April 30, 2026.
Your impacted Lambda functions using the Node.js 20.x runtime are listed on the 'Affected resources' tab of your AWS Health Dashboard.
This notification is generated for functions using the Node.js 20.x runtime for the $LATEST function version. The following command shows how to use the AWS CLI [3] to list all functions in a specific region that is using Node.js 20.x, including published function versions. To find all such functions in your account, repeat the following command for each region:
aws lambda list-functions --region us-east-1 --output text --query "Functions[?Runtime=='nodejs20.x'].FunctionArn"
Starting 180 days before deprecation, you can also use Trusted Advisor to identify functions using the Node.js 20.x runtime [4].
If you have any concerns or require further assistance, please contact AWS Support [5].
Runtime deprecation may occasionally be deferred for operational reasons. You can check active notifications in AWS Health and the Lambda runtime documentation [6] for the current schedule.
Relevant Logs
Additional Context (Screenshots, etc.)
No response