You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreamorosi opened this issue
Aug 29, 2023
· 2 comments
· Fixed by #1802
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
On November 23, 2023 Powertools for AWS Lambda (TypeScript) will end support for Node.js 14.
This action follows Node.js 14 reaching End-Of-Life (EOL) on April 30, 2023 and is scheduled just one business day before the date in which AWS Lambda will no longer apply security patches and other updates to the runtime.
We recommend that you upgrade your existing Node.js 14 functions to Node.js 18 before November 23, 2023.
End of support does not impact existing functions and functions using versions of Powertools for AWS Lambda (TypeScript) released before November 23, 2023, however starting from this date we will not guarantee compatibility with Node.js 14.
You can use the following AWS CLI command to list all functions in a specific region using Node.js 14, including published function versions:
Note
Make sure to replace the value of the --region flag and run this command in each region you have Lambda functions workloads
aws lambda list-functions --function-version ALL --region <Region> --output text --query "Functions[?Runtime=='nodejs14.x'].FunctionArn"
Why is this needed?
Starting from November 27, 2023 we will no longer be able to deploy new Lambda functions using the Node.js 14 runtime, this means we won't be able to run integration tests for new code changes.
With this in mind, we will stop supporting the runtime altogether.
Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
confirmed
The scope is clear, ready for implementation
labels
Aug 29, 2023
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or 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.
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Summary
Important
On November 23, 2023 Powertools for AWS Lambda (TypeScript) will end support for Node.js 14.
This action follows Node.js 14 reaching End-Of-Life (EOL) on April 30, 2023 and is scheduled just one business day before the date in which AWS Lambda will no longer apply security patches and other updates to the runtime.
We recommend that you upgrade your existing Node.js 14 functions to Node.js 18 before November 23, 2023.
End of support does not impact existing functions and functions using versions of Powertools for AWS Lambda (TypeScript) released before November 23, 2023, however starting from this date we will not guarantee compatibility with Node.js 14.
You can use the following AWS CLI command to list all functions in a specific region using Node.js 14, including published function versions:
Note
Make sure to replace the value of the
--region
flag and run this command in each region you have Lambda functions workloadsWhy is this needed?
Starting from November 27, 2023 we will no longer be able to deploy new Lambda functions using the Node.js 14 runtime, this means we won't be able to run integration tests for new code changes.
With this in mind, we will stop supporting the runtime altogether.
Which area does this relate to?
Governance
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: