Node runtime needs bumping.

[prozz]

Environment information

env info is unrelated to this feature request

Describe the feature

AWS recently send a notification that LambdaRuntime.NODEJS_20_X will end its life. Bumping it to suitable runtime early would be good for end users.

Use case

Amplify applications will stop working.

[pahud]

Hi @prozz,

Thank you for raising this concern about Lambda runtime versions.

I'd like to clarify that Node.js 20 (NODEJS_20_X) is currently in active support and will remain supported until April 30, 2026 according to AWS Lambda's runtime support policy. If you received a notification about end-of-life, it may be referring to an older runtime version (like Node.js 16 or 18) rather than Node.js 20.

That said, Amplify Backend already supports Node.js 22! You can use it today by explicitly specifying the runtime in your function definition:

amplify-backend/packages/backend-function/src/factory.ts

Line 180 in b402da9

runtime?: NodeVersion;

The defineFunction implementation currently defaults to Node.js 20 as it's the oldest actively supported LTS version, following the principle of maximum compatibility. As Node.js 20 approaches its end-of-life in 2026, the team will likely update the default to Node.js 22.

Could you share more details about the notification you received? This would help us understand if there's a specific concern we should address.

Let me know if it clarifies.

[prozz]

Notification is available globally on my AWS account, not inside Amplify console, and starts like this:

[Action Required] AWS Lambda Node.js 20.x end-of-life [AWS Account: XXX]

Since I don't know release schedules I decided to raise an issue as it affects way more people than just me.

I am defining Amplify lambdas just for Cognito integration and did them according to the docs. Wasn't aware runtime is exposed, so thanks for the tip!

Thanks a lot for clarification 🙇