Amplify studio is generating deprecated Node.js 16.x runtime Lambda functions

[mike1975-AWS]

Hi,

Yesterday, I received a warning email from AWS regarding the support for Node.js v16 in AWS Lambda functions. A part of the message is posted below:

"We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the Node.js 16 runtime. We are ending support for Node.js 16 in Lambda on June 12, 2024. This follows Node.js 16 End-Of-Life (EOL) reached on September 11, 2023 [1]."

To pinpoint the issue, I created a new app from scratch with Amplify Studio (Gen 1). In the new app, I also added authentication through Amplify Studio. However, I discovered that Amplify Studio creates Lambda functions and sets the environment again to Node.js v16. :(

Is this a bug in Amplify Studio? Can we somehow address this issue and set the Node.js environment to the latest version (v18/v20)? Has someone faced and solved this issue so far?

[chrislrobert]

I've wasted an inordinate amount of time trying to resolve this on my own, and had thought the issue was in the app/CLI — so ended up posting an issue at aws-amplify/amplify-cli#13565. To be specific, these are the problematic Lambda functions in need of updating:

1. amplify-login-custom-message-[ID number]
2. amplify-login-create-auth-challenge-[ID number]
3. amplify-login-define-auth-challenge-[ID number]
4. amplify-login-verify-auth-challenge-[ID number]

I see those in both my dev and my production accounts, dating back to when I set up the Amplify environments. Really unsure how to resolve this...

[ykethan]

Hey @chrislrobert the Amplify Studio informed me the fix for this is currently inflight and should provide an update here once this is released.

[chrislrobert]

Fantastic, thank you!

…

On Thu, Feb 1, 2024, 12:56 PM Kethan sai ***@***.***> wrote: Hey @chrislrobert <https://github.com/chrislrobert> the Amplify Studio informed me the fix for this is currently inflight and should provide an update here once this is released. — Reply to this email directly, view it on GitHub <#1085 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACB3IHUA3BCYEHQLSNWHUMLYRPJN7AVCNFSM6AAAAABBOWD5IWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRRHA4TQNRTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ykethan]

@chrislrobert @mike1975-AWS hey folks, the Studio login functions have been updated. For the changes to take effects, you will need to disable and re-enable studio. Refer to documentation providing detailed steps.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.