# Deployment not respecting "runtime: nodejs14.x" when creating "projectname-stage-custom-resource-existing-cup"

**URL:** https://forum.serverless.com/t/deployment-not-respecting-runtime-nodejs14-x-when-creating-projectname-stage-custom-resource-existing-cup/19029
**Category:** Serverless Framework
**Created:** [June 27, 2023, 9:19am UTC](https://forum.serverless.com/t/deployment-not-respecting-runtime-nodejs14-x-when-creating-projectname-stage-custom-resource-existing-cup/19029 "2023-06-27T09:19:26Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![AEsmerio](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/aesmerio/32/7523_2.png) [@AEsmerio](https://forum.serverless.com/u/AEsmerio)
#### Post date: [June 27, 2023, 9:19am UTC](https://forum.serverless.com/t/deployment-not-respecting-runtime-nodejs14-x-when-creating-projectname-stage-custom-resource-existing-cup/19029/1 "2023-06-27T09:19:26Z")

</div>

Hi all

First: I’d like to understand which service is creating this Lambda function “projectname-stage-custom-resource-existing-cup”. I’ve not seen it in the documentation that I read.

Second: I was using Serverless v2.72. My serverless.yml was/still set to use nodejs.14x this “projectname-stage-custom-resource-existing-cup” was deployed to AWS using nodejs.12x, which is causing errors today as AWS no longer allows nodejs.12x deployments. It took a while to realise that I needed to update Serverless. I’m now using v3.33. This function “projectname-stage-custom-resource-existing-cup” now uses nodejs.16x. In both scenarios, the deployment does not respect my “runtime” settings.

Am I missing something to respect the NodeJs runtime version?