Autor Thema: AWS Lambda  (Gelesen 366 mal)

Offline franky08

  • Hero Member
  • *****
  • Beiträge: 4177
  • jetzt DBLog befreit
AWS Lambda
« am: 11 Mai 2018, 12:09:59 »
Hallo, habe eben folgende Mail bekommen:
Zitat
AWS Lambda: Node.js v4.x is now EOL, please migrate your functions to a newer runtime version [AWS Account: xxxxxx
Hello,

Your AWS Account currently has one or more Lambda functions configured to use the Node.js v4.3 runtime. The Node Foundation declared End-of-Life (EOL) for Node.js v4 on April 30, 2018. As a result, this version of Node.js is no longer receiving bug fixes, security updates, or performance improvements from the Node Foundation. Per the AWS Lambda runtime support policy [2] , language runtimes that have been end-of-lifed by the supplier are deprecated in AWS Lambda. While invocations of Lambda functions configured to use Node.js v4.3 will continue to work normally, the ability to create new Lambda functions configured to use the Node.js v4.3 runtime will be disabled on July 31, 2018. Code updates to existing functions using Node.js v4.3 will be disabled on October 31, 2018. We strongly encourage you to update all your functions to a newer version of Node.js (v6.10 or v8.10) so that you continue to benefit from important security, performance, and functionality enhancements offered by the Node Foundation via more recent releases.

Which version of Node.js should I migrate to?

While Node.js v6.10 is available on AWS Lambda, we recommend that you migrate directly to Node.js v8.10, a newer version with improved ES6 support and other language and API improvements. The AWS Lambda programming model for Node.js v8.10 maintains backwards compatibility with previous versions to simplify portability. We recommend that you test your Lambda function to validate its behavior on the newer version of Node.js.


Was sollte jetzt unternommen werden?

VG
Frank
Debian Wheezy auf ZBOX nano (240GB SSD) FHEM2FHEM an 2xRaspiB
22Zoll ViewSonic als Infodislay (WVC)
3xHMLAN mit vccu ,fhem5.8, WH1080 fowsr an 2.RaspiB
Raspi B mit COC für ESA 2000 und CO2-Sensor
ECMD an AVR-NET-IO mit DAC u. ADC an Junkers Stetigregelung, Siemens LOGO!8, JeeLink

Online MadMax-FHEM

  • Hero Member
  • *****
  • Beiträge: 3793
  • NIVEAu ist keine Creme...
Antw:AWS Lambda
« Antwort #1 am: 11 Mai 2018, 13:22:08 »
Hab noch nichts bekommen...
...aber wohl andere:

https://forum.fhem.de/index.php/topic,81790.msg801166.html#msg801166

Gruß, Joachim
FHEM 5.8 PI3: HM-CFG-USB, 40x HM, ZWave-USB, 6x ZWave, EnOcean-PI, 3x EnOcean, DashButtons, CO2, ESP-Multisensor, FireTV, NanoLeaf, ...
FHEM 5.8 PI2: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, KODI, ha-bridge, ...
FHEM 5.8 PI3 (Test): HM-MOD-PCB, Alexa (alexa-fhem), Google Home

Offline Benni

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1799
  • FHEMinist
Antw:AWS Lambda
« Antwort #2 am: 11 Mai 2018, 15:05:04 »
Was sollte jetzt unternommen werden?

Erst mal Ruhe bewahren, nochmal lesen und dann verstehen, was in der Ankündigung geschrieben wird  ;)

https://forum.fhem.de/index.php/topic,81790.msg801311.html#msg801311
FHEM (FL 9.9) (configDB+DbLog) auf Debian Wheezy.
Jede Menge HM mit 2x HMUART (WeMos+esp-link) über VCCU.
UniRoll an CUL868. Sebury F2-2 RFID über ESPEasy
Module: 98_rssFeed und 98_QRCode