Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js 14 runtime is reaching EOL #708

Closed
ilpianista opened this issue Aug 28, 2023 · 1 comment
Closed

Node.js 14 runtime is reaching EOL #708

ilpianista opened this issue Aug 28, 2023 · 1 comment
Labels
status: duplicate This issue or pull request already exists

Comments

@ilpianista
Copy link

Is your idea related to a problem? Please describe.

Hello,

We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using the Node.js 14 runtime.

We are ending support for Node.js 14 in AWS Lambda. This follows Node.js 14 End-Of-Life (EOL) reached on April 30, 2023 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 27, 2023, Lambda will no longer apply security patches and other updates to the Node.js 14 runtime used by Lambda functions, and functions using Node.js 14 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 14 runtime. Starting January 25, 2024, you will no longer be able to update existing functions using the Node.js 14 runtime.

We recommend that you upgrade your existing Node.js 14 functions to Node.js 18 before November 27, 2023.

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 solution you'd like

Upgrade the lambda to Node.js 16.

P.S. Don't attach files. Please, prefer add code snippets directly in the message body.

@dlpzx
Copy link
Contributor

dlpzx commented Sep 4, 2023

@ilpianista, thanks for the issue! I will close it as it is referenced in #721 and #655

@dlpzx dlpzx closed this as completed Sep 4, 2023
@dlpzx dlpzx added the status: duplicate This issue or pull request already exists label Sep 4, 2023
dlpzx pushed a commit that referenced this issue Sep 4, 2023
### Feature or Bugfix
- Bugfix

### Detail
update auth-at-edge semantic version to latest 2.1.7

### Relates
- #708 
- #709 

### Security
N/A

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants