search

aws-solutions / qnabot-on-aws

AWS QnABot is a multi-channel, multi-language conversational interface (chatbot) that responds to your customer's questions, answers, and feedback. The solution allows you to deploy a fully functional chatbot across multiple channels including chat, voice, SMS and Amazon Alexa.
https://aws.amazon.com/solutions/implementations/aws-qnabot
Apache License 2.0
401 stars 253 forks source link

End of support for Node.js 16, update to Node.js 20 #673

Closed amendlik closed 10 months ago

amendlik commented 11 months ago

Is your feature request related to a problem? Please describe. I received an end-of-support notification for Lambda functions using Node.js 16:

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].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages. Starting on June 12, 2024, Lambda will no longer apply security patches and other updates to the Node.js 16 runtime used by Lambda functions, and functions using Node.js 16 will no longer be eligible for technical support. Also, Node.js 16 will no longer be available in the Console, although you can still create and update functions using Node.js 16 via AWS CloudFormation, the AWS CLI, AWS SAM, or other tools. Starting July 15, 2024, you will no longer be able to create new Lambda functions using the Node.js 16 runtime. Starting August 15, 2024, you will no longer be able to update existing functions using the Node.js 16 runtime.

We recommend that you upgrade your existing Node.js 16 functions to Node.js 20 before June 12, 2024. A list of your Node.js 16 functions can be found in the 'Affected resources' tab of the AWS Health Dashboard.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.

Describe the feature you'd like Per the recommendation above, update functions to use the Node.js 20 runtime.

abhirpat commented 11 months ago

Hi @amendlik , could you please confirm which version of QnaBot you have deployed?

Kindly note that the latest QnaBot is already using Node 18 for it's lambdas and it is available for you to upgrade. Thus, you should stop receiving these Node 16 EOL notifications once you have upgraded to latest QnaBot version.

amendlik commented 10 months ago

You are right. I see that the Node version was moved to 18 recently.

thejang90 commented 7 months ago

Hi @amendlik, what is this mean "you will no longer be able to update existing functions using the Node.js 16 runtime."? Are we not able to run lambda using the Node.js 16?. And, Do we convert code which exist fucntion to fit node.js 18 runtime?

amendlik commented 7 months ago

Hi @amendlik, what is this mean "you will no longer be able to update existing functions using the Node.js 16 runtime."? Are we not able to run lambda using the Node.js 16?. And, Do we convert code which exist fucntion to fit node.js 18 runtime?

@thejang90 - I don't exactly know what that means. I was only quoting the language in the EOS notification I received from AWS.