Wrong Node Version Through CLI

[brazen knot]

Any ideas how the node version that resources use are set through the CLI? Whenenver I try to run amplify auth update and add a pre-signup trigger, the auth trigger lambda gets created with Node12 instead of a newer supported version. My local version of node is 18.

[limpid stratus]

hey what version of the CLI are you using? iirc those were all updated to deploy using node16

[red hare]

@limpid stratus I am having same issue with the CLI

[limpid stratus]

@red hare you'll need to manually update the runtime version for the affected Functions in their associated CloudFormation template

[red hare]

What's the node Js version supported? I'm running on ver 18

[limpid stratus]

Lambda supports node 18, but they switched over from aws-sdk v2 to v3, which means you will need to:

• port any code using sdk v2 to v3
• install the relevant v3 packages to mock locally

otherwise you can replace nodejs12.x with nodejs16.x and still use sdk v2

[brazen knot]

Sorry late replying. We were on vacation. I am using 9.2.1. I was trying to push a new Lambda, so sounds like I need to update the Cloud Formation manually as a workaround. After that will it start using the correct vs? Wondering how it decides what vs of NodeJS to use?