-----Original Message-----
From: Amazon Web Services, Inc. <no-reply-aws@amazon.com>
Sent: Wednesday, June 2, 2021 2:20 PM<p>Hello,
Q. What is happening?
A. We are ending support for Node.js 10 in AWS Lambda on July 30, 2021. This follows the Node.js language governing body declaring Node.js 10 end of life as of April 30, 2021 [1].<p>Q. What does end of support for Node.js 10 in Lambda mean?
A: As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting July 30, 2021, Lambda will no longer apply security patches and other updates to the Node.js 10 runtime used by Lambda functions, and functions using Node.js 10 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 10 runtime. Starting Aug 30, 2021, you will no longer be able to update existing functions using the Node.js 10 runtime.<p>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.<p>...
Q. How do I know if I have any functions using Node.js 10?
aws lambda list-functions --function-version ALL --output text --query "Functions[?Runtime=='nodejs10.x'].FunctionArn"<p>Q. What do I need to do?
A. You should migrate your existing Node.js 10 Lambda functions to Node.js 14, which is the latest supported Node.js version in Lambda [4]. Node.js 14 is not yet supported by Lambda@Edge, so Lambda@Edge functions should be upgraded to Node.js 12. By moving to a supported runtime version you will continue to benefit from important ... enhancements offered by more recent releases.<p>Q. What if I need additional help?
A. Please contact us through AWS Support [5], the AWS Lambda Developer Forum [6], or your AWS account team should you have any questions or concerns.<p>Sincerely,
Amazon Web Services