Skip to content

Node Old Version

0

Our app is using an old version of Meteor (.11.1 ) and node (12.16.1 ), we are working on migrating to Meteor 2.14 and node 14.21.4 and then we will continue to the latest version of Meteor (3.1.2) with node 22.13.1, but this last step will take us some time. Please can you tell me when node 12.16.1 will no longer work to make deployments and run our app and when node 14.x will no longer work with lambda functions. More info: our code is build using Docker on Linux standard 5.0 What should we do to continue with these old version until our migration is done?

asked 2 years ago211 views

1 Answer
1

I understand your concern about using older versions of Node.js in your application and AWS Lambda functions. Let me provide you with some important information regarding the support and deprecation of these Node.js versions.

For Node.js 12.16.1: This version is already deprecated and no longer supported. AWS Lambda has already ended support for Node.js 12.x, and you cannot create or update Lambda functions using this runtime. It's crucial to move away from this version as soon as possible, as it may have unpatched security vulnerabilities and could stop working at any time.

For Node.js 14.x: Node.js 14.x is also deprecated for AWS Lambda functions. As of January 9, 2024, you can no longer create new Lambda functions using Node.js 14.x. Existing functions using this runtime may continue to run, but you cannot update them, and they may have security vulnerabilities.

Regarding your migration plan: Your plan to migrate to Meteor 2.14 with Node.js 14.21.4 is a step in the right direction, but it's important to note that this is still an outdated version. While it may work for your application build process using Docker on Linux standard 5.0, it's not supported for AWS Lambda functions.

Recommendations:

  1. Accelerate your migration plan if possible. The sooner you can move to supported versions, the better for security and functionality.
  2. For your application build process, you may be able to continue using Node.js 14.x temporarily, but be aware that it's no longer receiving security updates.
  3. For AWS Lambda functions, you should aim to use at least Node.js 16.x, but preferably Node.js 18.x or 20.x, which are currently supported.
  4. If you absolutely must continue using Node.js 14.x for Lambda functions temporarily, you may need to contact AWS Support for special arrangements, but this is not a long-term solution.
  5. Consider separating your application's Node.js version from your Lambda functions' version. This way, you can update Lambda functions to a supported runtime while continuing your gradual application migration.

Remember, using outdated runtimes poses security risks and may lead to unexpected issues. It's crucial to prioritize updating to supported versions as soon as possible to ensure the security and reliability of your application and Lambda functions.
Sources
rollback the runtime to node v14 | AWS re:Post
Announcing the end of support for Node.js 16.x in the AWS SDK for JavaScript (v3) | AWS Developer Tools Blog
Managing AWS Lambda runtime upgrades | AWS Compute Blog
aws rekognition custom labels | AWS re:Post

answered 2 years ago

AWS
EXPERT

reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.