AWS Lambda

The runtime parameter of nodejs18.x is no longer supported for creating or updating AWS Lambda functions

The runtime parameter of nodejs18.x is no longer supported for creating or updating AWS Lambda functions

What it means

AWS Lambda is blocking create/update operations on a deprecated Node.js runtime.

Why it happens

Per the AWS Lambda runtime deprecation table, nodejs16.x and nodejs18.x are both deprecated (patches stopped) and share the same block dates: AWS blocks creating new functions on 2027-02-01 and updating existing ones on 2027-03-03 (AWS delayed both beyond the usual 30/60 days, in a cluster with nodejs20.x and several Python runtimes). The error fires once a deploy targets a runtime past its block date.

How to fix it

  1. Move to a currently supported runtime with adequate runway; EOLkits' current examples target nodejs24.x. Recheck AWS's table before scheduling.
  2. SAM/CloudFormation: `Runtime: nodejs24.x`. CDK: `runtime: lambda.Runtime.NODEJS_24_X`. Terraform: `runtime = "nodejs24.x"`. Serverless: `runtime: nodejs24.x`.
  3. Rebuild native addons for the Node.js 24 ABI and switch the bundled aws-sdk v2 to @aws-sdk v3 — see the related /fix pages.
  4. Redeploy and confirm with `aws lambda get-function-configuration --function-name <name> --query Runtime`.

Related deadline: Lambda Node.js 18 create/update restrictions — 2027-02-01.

Check configured patterns in your project

The free EOLkits scanner processes files in your browser and flags selected related patterns in supported IaC and dependency files. File names and contents are not uploaded; bounded aggregate file and finding counts may be sent. It is not a complete source or AWS-account scan.

Prefer a 10-second check? Paste your config into the free AWS EOL checker. Pasted input is not uploaded; bounded first-party usage events may be sent.

Primary source: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

Inspect the $299 report sample and availability →