Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Amazon email re Alexa interface?
Your AWS Account XXXXXXXXXXXXXX currently has 1 Node.js v0.10 functions that were active since March 06 2017. All Node.js v0.10 functions in your account (active or otherwise) must be migrated to Node.js v4.3 or they will be cease to operate on April 30th, 2017. AWS Lambda is deprecating the Node.js v0.10 runtime, and invocations on Node.js v0.10 functions will fail after this date.
Why is this happening?
The Node Foundation declared the End-of-Life (EOL) of Node.js v0.10 on Oct 31st 2016[1], which means that it has stopped receiving bug fixes, security updates and performance improvements. We recommend moving onto a version with life time support (LTS) supported with AWS Lambda today (Node v 4.3). We will continue to expand the list of available Node versions in future releases.
What has been done to date?
AWS Lambda announced Node.js v0.10 deprecation on November 2nd 2016 [2] and turned off the ability to create new functions using this runtime on January 11th 2017.
What do you need to do?
You must migrate all your Node.js v0.10 functions to Node.js v4.3 before April 30th 2017.
Your Node.js v0.10 functions will continue to work until April 30th 2017 as-is and support all features including making updates to code and configuration. This is to keep your production workloads running as usual and to provide time to execute the migration. After April 30th 2017, invocations to your Node.js v0.10 functions will fail and return an error.
Where can I get more information?
For more information on migrating to Node.js 4.3 on AWS Lambda, please see the "Transitioning Lambda Function Code to Node.js Runtime v4.3" section of our documentation in the AWS Lambda Developer Guide [3] and the AWS Lambda Forums [4].
For general information on Node v4.3 and migrating to it from Node v0.10, please see the Node community documentation related to this topic [5] [6].
For account specific information, e.g., to list all the functions in your account, please use the AWS CLI. Sample commands for a Unix/Bash environment are shown below:
# list counts of all functions Node.js functions aws lambda list-functions --query 'Functions
[*].[FunctionName, Runtime]' | awk '{ if ( /nodejs/) print $0}' lambdafunctions.txt | sort -n | uniq -c | sort ÔÇônr
# list Node.js v0.10 functions names
aws lambda list-functions --query 'Functions
[*].[FunctionName, Runtime]' | grep -v nodejs4.3 lambdafunctions.txt | grep -B1 nodejs| grep , | sort
[1]: Node FoundationÔÇÖs announcement of EOL:
[2]: AWS Lambda forum post for deprecation:
[3]: Transitioning to new Node JS runtime:
[4]: AWS Lambda Forum:
[5]: Upgrading Node.js v0.10 applications:
[6]: Changes between v0.10 and v4:
Amazon Web Services

Messages In This Thread
Amazon email re Alexa interface? - by Ron Haley - 03-13-2017, 03:11 PM
RE: Amazon email re Alexa interface? - by znelbok - 03-13-2017, 06:54 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Admin Interface Help Doesn't Work alexismtz13 1 249 04-28-2022, 01:14 PM
Last Post: Dean Roddey
  Driver for Amazon 4k Stick Darrie 3 510 01-15-2022, 02:21 PM
Last Post: znelbok
  CQSL Interface Driver connects but no control NightLight 3 568 10-26-2021, 01:12 PM
Last Post: NightLight
  Amazon AWS Message kblagron 1 513 10-16-2021, 03:49 PM
Last Post: Dean Roddey
  Amazon Echo integration rhosch 8 1,771 05-15-2021, 01:06 PM
Last Post: Bugman
  6.0.0 Interface Viewer - Action Trace Mark Stega 1 639 03-09-2021, 06:39 PM
Last Post: Dean Roddey
  Cannot Bind Interface to 80 gReatAutomation 1 936 11-05-2020, 04:18 PM
Last Post: Dean Roddey
  Help with email alerts xlurkr 5 1,020 08-17-2020, 04:54 PM
Last Post: Dean Roddey
  Check Box widget on WebRIVA vs Interface Viewer bryanb 1 1,045 04-23-2020, 06:15 AM
Last Post: bryanb
  Email account without authentication lleo 9 3,424 04-11-2020, 03:18 PM
Last Post: Dean Roddey

Forum Jump:

Users browsing this thread: 1 Guest(s)