Upgrade Lambdas to 10.x
See original GitHub issueSee if it takes an hour, if it takes longer, then reevaluate.
Feature Request
AWS is making Node.js 8.x EOL; if we have 8.x lambdas, we should upgrade them to 10.x.
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
┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.8 ┆Issue Number: DOCK-1055 ┆Sprint: Seabright Sprint 27 Barracuda ┆Issue Type: Story
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
New for AWS Lambda – Functions with Up to 10 GB of ...
Starting today, you can allocate up to 10 GB of memory to a Lambda function. This is more than a 3x increase compared...
Read more >Update deprecated Lambda run-times NODEJS_8_10 to ...
The Lambda run-time NodeJS 8.10 has been deprecated and you will no longer be able to create new functions with it on January...
Read more >AWS Lambda support for Node.js 10: Should you switch to ...
AWS Lambda support for Node.js 10 is due to end in August 2021. In this article, we compare Node.js 10 and Node.js 14....
Read more >Update NodeJS runtime from 8.10 to 10.x or 12.x - AWS ...
I have tried opening the Lambda function in the Lambda Function console and changing the runtime in the dropdown box that sits above...
Read more >Upgrading the Lambda@Edge Runtime
Deploy your current lambda function (built with node 10) to Cloudfront, specifying node 14 as the runtime · Rebuild the ABP Connector 1.21.2...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think either time works, I don’t think people rely on it enough that it should be a problem upgrading at any time, but upgrading during the release works too.
I think it’s tested on staging well enough. I debated whether to close this and create a new ticket for prod or just leaving this one open, but in any case we don’t want to forget to do it for prod. Probably safest to do it during the next release, IMHO.