This article explains how to ungrade the AWS Node.js runtime for a Lambda function, such as a Dropzone Connector or Actions Workflow.
When a given Node.js runtime version is "supported", it means AWS will automatically apply updates to the Node.js managed runtime as they become available. If AWS stops supporting your Node.js version, it does not mean your Lambda functions will stop working: it just means that updates will no longer be automatically applied.
Since it is always best to use a supported Node.js runtime, SendSafely advises that you upgrade your Lambda functions to use the latest Node.js version. All SendSafely Lambda functions are compatible with the latest versions of Node.js, so you can upgrade your existing functions without impacting your current workflows.
AWS will allow you to roll-back to a deprecated runtime for 60 days after deprecation. SendSafely advises you to update your runtime as soon as possible, to ensure your Lambda will function in the new runtime environment, and to enable a roll-back if it does not perform as expected.
You can find a list of AWS Node.js runtimes and their deprecation dates here.
How to Update
Upgrading a Lambda function is straight-forward and can be done via the console for the Lambda function. From the Code tab, scroll down to Runtime Settings and click Edit.
From the Edit runtime Settings screen, select the latest version of Node.js from the dropdown, then click Save.
You will a success banner indicating the runtime upgrade was successful.
How to Rollback Changes
If there is an issue with your Lambda function post updating, then you can easily rollback the change you made to the runtime using the Lambda console. Simply follow the same steps as you did to update the runtime, selecting your previous runtime from the dropdown menu.
Please note that you will not be able to rollback to Node.js v18 from November 1st 2025, so please update your Lambda functions as soon as possible.
SendSafely Support
If you have any issues upgrading or rolling back your Node.js runtime, please contact our Support team.
Comments
0 comments
Please sign in to leave a comment.