Skip to content

Do I need to upgrade Node.js version in both Git-based App Runner and ECR image deployments?

0

I received the AWS notification that App Runner will end support for Node.js 12, 14, 16, and 18 after December 1, 2025.

In my setup, I have two types of App Runner services:

Some services are integrated directly with GitHub, where I specify the Node.js runtime version in the configuration (currently using Node.js 16).

Other services are deployed from ECR container images, where the image is built using Node.js 18.

My question is:

  1. For Git-based services, I understand I need to update the runtime to Node.js 22.

  2. But for services running from ECR images, do I also need to rebuild and redeploy the image with Node.js 22, or will App Runner continue running the existing image without issues?

asked a year ago217 views

1 Answer
0

Yes, you will need to upgrade Node.js versions for both your Git-based App Runner services and your ECR container image deployments before the end of support date.

For your Git-based App Runner services currently using Node.js 16, you should update the runtime configuration to use Node.js 22, which is the current Active Long Term Support version. App Runner has announced that support for Node.js 12, 14, 16, and 18 will end on December 1, 2025.

For your ECR container image deployments using Node.js 18, you will also need to rebuild these images with Node.js 22 before the end of support date. While App Runner will continue to run your existing container images after the end-of-support date, these images will no longer receive security updates or bug fixes from the Node.js community, as Node.js 18.x reached its End of Life on April 30, 2025.

When upgrading to Node.js 22, be aware that App Runner now runs an updated build process for applications based on Node.js 22 and Node.js 18. This revised build process includes a pre-run section that isn't applicable to older runtime versions.

Also note that if you're using the AWS SDK in your applications, Node.js 22 includes AWS SDK for JavaScript version 3, whereas Node.js 16 and earlier included version 2. This may require code changes if you're using the SDK that's bundled with the runtime.

For a smooth transition, it's recommended to test your applications thoroughly in non-production environments after upgrading to ensure all dependencies and workflows function correctly with the new Node.js version.
Sources
Using the Node.js platform - AWS App Runner
Announcing the end of support for Node.js 18.x in AWS CDK | AWS DevOps & Developer Productivity Blog
Node.js 22 runtime now available in AWS Lambda | AWS Compute Blog

answered a year ago

EXPERT

reviewed a year 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.