# Ending support for Node.js 8.x on December 31, 2019 **URL:** \ **Category:** Rack (Version 2)\ **Created:** [October 21, 2019, 9:09am UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633 "2019-10-21T09:09:44Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![ali](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ali/32/15_2.png) [@ali](https://community.convox.com/u/ali)\ **Post date:** [October 21, 2019, 9:09am UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/1 "2019-10-21T09:09:44Z")
Hi, Bunch of us have started receiving the following notification from AWS: > 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 > > [1] [GitHub - nodejs/Release: Node.js Release Working Group](https://github.com/nodejs/Release) > [2] [Lambda runtimes - AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html) The gist of it is that, of course, we need to update; - `provider/kaws/formation/rack.yml` - `provider/aws/formation/app.json.tmpl` - `provider/aws/formation/rack.json` - `provider/aws/formation/g1/app.json.tmpl` - `provider/aws/templates/resource/webhook.tmpl` … which all refers to `Runtime: nodejs8.10`. ---
**Author:** ![ed\_convox](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ed_convox/32/101_2.png) [@ed\_convox](https://community.convox.com/u/ed_convox)\ **Post date:** [October 21, 2019, 2:51pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/2 "2019-10-21T14:51:16Z")
Hi @ali, We will release a rack update that will handle this before then, not to worry! 😊 Thanks, Ed ---
**Author:** ![mattbriancon](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/mattbriancon/32/16_2.png) [@mattbriancon](https://community.convox.com/u/mattbriancon)\ **Post date:** [November 2, 2019, 8:53pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/3 "2019-11-02T20:53:59Z")
Aren’t many (most? all?) of the Node.js Lambdas just tiny wrappers around a Go program that does the real work? Lambda has supported Go for ~2 years. Why not cut out the overhead and just switch everything to use Go directly? ---
**Author:** ![ddollar](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ddollar/32/3_2.png) [@ddollar](https://community.convox.com/u/ddollar)\ **Post date:** [November 3, 2019, 1:27am UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/4 "2019-11-03T01:27:55Z")
Almost all of the Lambda functions have been converted to pure Go. The functions in question are inline pure-Javascript embedded in the CloudFormation templates. We rolled this back because CloudFormation had not yet finished rolling out support for inline nodejs10 in all regions. ---
**Author:** ![mattbriancon](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/mattbriancon/32/16_2.png) [@mattbriancon](https://community.convox.com/u/mattbriancon)\ **Post date:** [November 6, 2019, 2:50pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/5 "2019-11-06T14:50:37Z")
One more that needs to be converted: the syslog Lambda. ---
**Author:** ![ali](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ali/32/15_2.png) [@ali](https://community.convox.com/u/ali)\ **Post date:** [November 11, 2019, 12:44pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/6 "2019-11-11T12:44:45Z")
Are there any updates here please about the general availability of the runtime across all regions? ---
**Author:** ![edward](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/edward/32/47_2.png) [@edward](https://community.convox.com/u/edward)\ **Post date:** [December 13, 2019, 3:25pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/7 "2019-12-13T15:25:06Z")
I am unable to upgrade my Rack - because of this issue: > [@IAM Error upgrading rack](https://community.convox.com/t/iam-error-upgrading-rack/512): > > Updating from version: 20190126182547 Anyone familiar with this issue? CREATE\_IN\_PROGRESS VolumeTarget0 CREATE\_IN\_PROGRESS VolumeTarget1 CREATE\_FAILED VolumeTarget0 The IAM identity making this call has an IAM policy that is too large. Reduce the size of the policy and try again. (Service: AmazonElasticFileSystem; Status Code: 400; Error Code: BadRequest; Request ID: 21104a41-6c06-11e9-8946-35b35ddaba77) CREATE\_FAILED VolumeTarget1 The IAM identity making this call has an IAM policy that is to… Can I get a heads-up on what I could expect to happen if this date lapses before we have a solution? Our our running systems at serious risk? ---
**Author:** ![ed\_convox](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ed_convox/32/101_2.png) [@ed\_convox](https://community.convox.com/u/ed_convox)\ **Post date:** [December 16, 2019, 2:30pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/8 "2019-12-16T14:30:04Z")
We’ve now re-released the update to Nodejs10.x as it appears that AWS has rolled out support across all regions finally! > [@\[20191211175055\] Lambda Node.js Upgrade](https://community.convox.com/t/20191211175055-lambda-node-js-upgrade/666): > > Upgrades internal Node.js lambda functions to nodejs10.x in response to a recent AWS deprecation notice. 😊 ---
**Author:** ![ali](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ali/32/15_2.png) [@ali](https://community.convox.com/u/ali)\ **Post date:** [December 16, 2019, 3:07pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/9 "2019-12-16T15:07:19Z")
Thanks! ---
**Author:** ![luciano.arcudi](https://avatars.discourse-cdn.com/v4/letter/l/eada6e/32.png) [@luciano.arcudi](https://community.convox.com/u/luciano.arcudi)\ **Post date:** [January 8, 2020, 10:57am UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/10 "2020-01-08T10:57:58Z")
Good morning all how should I proceed in order to update the lambda/node version? Is there any standard procedure or update the rack is enough? ---
**Author:** ![julian](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/julian/32/35_2.png) [@julian](https://community.convox.com/u/julian)\ **Post date:** [January 10, 2020, 11:33pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/11 "2020-01-10T23:33:35Z")
We’ve updated our racks and apps, but there are still a few lambda functions using node 8: - `convox-*-NotifierHandler-*` - `*-console-*-Forwarder-*` Is there a way to update these? I think they might be rack resources (syslog/webhook)? ---
**Author:** ![andreas.nilsson](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@andreas.nilsson](https://community.convox.com/u/andreas.nilsson)\ **Post date:** [January 14, 2020, 9:12am UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/12 "2020-01-14T09:12:27Z")
We’re currently unable to launch new resources in AWS due to this error. `020-01-14 10:08:28 UTC+0100 NotifierHandler CREATE_FAILED The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: dd789c70-9912-44de-8010-a726b8102165)` This is when adding the AWS-Convox runtime integration. ---
**Author:** ![ed\_convox](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ed_convox/32/101_2.png) [@ed\_convox](https://community.convox.com/u/ed_convox)\ **Post date:** [January 14, 2020, 2:37pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/13 "2020-01-14T14:37:33Z")
@julian, @andreas.nilsson Thanks for flagging this up, digging in and found the old function so expect an update soon! Thanks, ---
**Author:** ![julian](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/julian/32/35_2.png) [@julian](https://community.convox.com/u/julian)\ **Post date:** [January 14, 2020, 9:39pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/14 "2020-01-14T21:39:10Z")
@andreas.nilsson I ran into this yesterday. A workaround is to edit the cloudformation template and change the engine to `nodejs12.x` by hand, then copy the parameters (AccountId, ExternalId, IntegrationUrl) in from the original ---
**Author:** ![ed\_convox](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/ed_convox/32/101_2.png) [@ed\_convox](https://community.convox.com/u/ed_convox)\ **Post date:** [January 16, 2020, 12:26pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/15 "2020-01-16T12:26:27Z")
Hey guys, the issue with the AWS runtime integration is now fixed. Please try again! Thanks, Ed ---
**Author:** ![andreas.nilsson](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@andreas.nilsson](https://community.convox.com/u/andreas.nilsson)\ **Post date:** [January 16, 2020, 3:04pm UTC](https://community.convox.com/t/ending-support-for-node-js-8-x-on-december-31-2019/633/16 "2020-01-16T15:04:03Z")
Seems to working as intended so far. Thanks!