search

assertible / lambda-cloudwatch-slack

Send AWS CloudWatch notifications to a Slack channel using Lambda
https://assertible.com/blog/npm-package-lambda-cloudwatch-slack
MIT License
482 stars 249 forks source link

AWS Warnings about Node Version #50

Open frankiesimon opened 4 years ago

frankiesimon commented 4 years ago

AWS recently sent this email to all users with lambdas using Node.js 8.10:

We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 8.10, which will reach its EOL at the end of 2019.

What’s happening?

The Node community has decided to end support for Node.js 8.x on December 31, 2019 [1]. From this date forward, Node.js 8.x will stop receiving bug fixes, security updates, and/or performance improvements. To ensure that your new and existing functions run on a supported and secure runtime, language runtimes that have reached their EOL are deprecated in AWS [2].

For Node.js 8.x, there will be 2 stages to the runtime deprecation process:

  1. Disable Function Create – Beginning January 6, 2020, customers will no longer be able to create functions using Node.js 8.10

  2. Disable Function Update – Beginning February 3, 2020, customers will no longer be able to update functions using Node.js 8.10

After this period, both function creation and updates will be disabled permanently. However, existing Node 8.x functions will still be available to process invocation events.

What do I need to do?

We encourage you to update all of your Node.js 8.10 functions to the newer available runtime version, Node.js 10.x[3]. You should test your functions for compatibility with the Node.js 10.x language version before applying changes to your production functions.

Can this be addressed in configuration? Is there a way to update this without redeploying? If I do redeploy will it mess up the existing configuration?

mherger commented 4 years ago

I run npm install node-lambda@latest before deploying. This would update the node-lambda module which now uses Node 10 by default. I'm sure there's a better/more flexible way to do it. But that was quick and painless.

dharshan commented 4 years ago

@mherger Thanks. Worked for me.