Auth Trigger Template still uses Node 12

[SebastianStamm]

Is this feature request related to a new or existing Amplify category?

auth

Is this related to another service?

Lambda

Describe the feature you'd like to request

With Node 12 being EOL, the runtime for the auth trigger function should be updated to Node 14 to be consistent with the runtime used in other environments. It currently still uses Node 12:

amplify-cli/packages/amplify-category-auth/src/provider-utils/awscloudformation/utils/generate-auth-trigger-template.ts

Line 91 in aaf2210

runtime: lambda.Runtime.NODEJS_12_X,

Describe the solution you'd like

Simply updating to lambda.Runtime.NODEJS_14_X should do the trick.

Describe alternatives you've considered

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• ⚠️ This feature might incur a breaking change

[josefaidt]

Hey @SebastianStamm 👋 thanks for raising this! While I was not able to see the Node 12.x runtime version be applied to a few of the auth triggers I added to my sample auth resource, I do think this is a great callout and should be updated. Perhaps we can also consider bumping to Node 16 across all functions.

Marking as a bug 🙂

[joekiller]

It nice to see the PR #10890 to fix this. I was going to comment re @josefaidt's idea of considering Node 16 in case anyone else reviews this issue. The current CDK sdk behind the cli and dependent https://github.com/aws-amplify/amplify-category-api only go to node 14. I attempted to do a slightly heavier lift to 1.168.0 but ran into some test breakage on amplify-category-api and just dropped the effort due to timeboxing. just an FYI why node 16 is "harder".

[hein-j]

Related - aws-amplify/amplify-studio#639

[christian-weiss-df]

AWS notification e-mail recommends to migrate from NodeJS 12 to NodeJS 16.
We should skip NodeJS 14. My2ct