# Autogenerated Lambdas Node Version

**URL:** <https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204>\
**Category:** Serverless Framework\
**Created:** [November 5, 2021, 11:51pm UTC](https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204 "2021-11-05T23:51:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattcarter](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@mattcarter](https://forum.serverless.com/u/mattcarter)\
**Post date:** [November 5, 2021, 11:51pm UTC](https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204/1 "2021-11-05T23:51:24Z")

</div>

Upgrading SLS version… running into the following error:

```auto
An error occurred: CustomDashresourceDashexistingDashs3LambdaFunction - Resource handler returned message: "The runtime parameter of nodejs10.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs14.x) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: e692cce2-ba36-48d5-b953-fe488566a3a9, Extended Request ID: null)" (RequestToken: 71ea2582-6885-1a06-1bfa-e77ac97c774e, HandlerErrorCode: InvalidRequest).

```

Don’t see anywhere to define the node version of these lambdas… any help is appreciated.

---

<div class="post-metadata">

**Author:** ![stevestorey](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/stevestorey/32/6154_2.png) [@stevestorey](https://forum.serverless.com/u/stevestorey)\
**Post date:** [November 12, 2021, 10:11pm UTC](https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204/2 "2021-11-12T22:11:04Z")

</div>

In your serverless.xml, you’ll want something like this:

```auto
provider:
  name: aws
  runtime: nodejs14.x

```

to use NodeJS 14. Looks like it’s not a sls upgrade that will have caused it, but a change on the AWS side to remove support for node 10

---

<div class="post-metadata">

**Author:** ![mattcarter](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@mattcarter](https://forum.serverless.com/u/mattcarter)\
**Post date:** [November 12, 2021, 10:28pm UTC](https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204/3 "2021-11-12T22:28:04Z")

</div>

Agreed, the underlying issue is the removal of the runtime support.

The lambas being deployed are python ones, so the serverless.yml already has

```auto
runtime: python3.7

```

defined in it.

But it turns out, updating another plugin…_serverless-domain-manager_ fixes the issue.

---

<div class="post-metadata">

**Author:** ![subhnet](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/subhnet/32/6388_2.png) [@subhnet](https://forum.serverless.com/u/subhnet)\
**Post date:** [November 26, 2021, 6:39am UTC](https://forum.serverless.com/t/autogenerated-lambdas-node-version/16204/4 "2021-11-26T06:39:50Z")

</div>

Hi @mattcarter, I am also facing the same problem but in my case, the plugins are different from yours.

```auto
plugins:
  - serverless-python-requirements
  - serverless-plugin-existing-s3

```

Did you specify a particular version like below to fix it?

```auto
plugins:
  - serverless-plugin-existing-s3@2.5.2

```