Node.js 8.10 runtime now available in AWS Lambda

Was waiting for this update! Running Puppeteer related projects will now be a ton easier for ad hoc project.<p>I&#x27;m pretty deep into this with <a href="https:&#x2F;&#x2F;checklyhq.com" rel="nofollow">https:&#x2F;&#x2F;checklyhq.com</a> so not really an &quot;ad hoc&quot; user. Some open concerns for &quot;real&quot; production use are still:<p>- cost: memory heavy (1,5Gb) lambda get costly quickly<p>- stability: No reason to assume this is bad, but running a Chromium browser in Docker is&#x2F;was pretty tricky<p>- startuptime: Booting Chrome might be a time suck<p>Coupling this with SQS triggers for Lambda might make spinning up VM&#x27;s obsolete for my business.

This is massive for AWS Lambda (and we&#x27;ve waited a long time for this). We can now use async&#x2F;await without transpiling our code. Thereby making it more readable.<p>We should hopefully see improved performance and startup times.

It was said back in a blog post for the introduction of aws batch, but when will we be able to also use lambda functions in a batch environment? (The job isn’t too complex, it just needs to run longer than 5 minutes (an hour or two))

Has anyone already managed to get this working? I currently get:<p><pre><code> expected runtime to be one of [nodejs4.3 nodejs6.10 java8 python2.7 python3.6 dotnetcore1.0 dotnetcore2.0 nodejs4.3-edge go1.x], got nodejs8.10 </code></pre> It might be due to my using TerraForm and that needing an update, but it&#x27;s also not yet listed in the docs: <a href="https:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;lambda&#x2F;latest&#x2F;dg&#x2F;API_CreateFunction.html#SSS-CreateFunction-request-Runtime" rel="nofollow">https:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;lambda&#x2F;latest&#x2F;dg&#x2F;API_CreateFunct...</a><p>Or perhaps it&#x27;s not available in all regions yet?

Perhaps this will make headless chromium easier<p><a href="https:&#x2F;&#x2F;www.npmjs.com&#x2F;package&#x2F;@browserless&#x2F;aws-lambda-chrome" rel="nofollow">https:&#x2F;&#x2F;www.npmjs.com&#x2F;package&#x2F;@browserless&#x2F;aws-lambda-chrome</a>

This update was a very long time coming, so I&#x27;m grateful that it finally happened.<p>Still, it&#x27;s disappointing that they couldn&#x27;t change course (ever so slightly!) to accommodate the 8.11.0 <i>security update</i> from a week ago: <a href="https:&#x2F;&#x2F;nodejs.org&#x2F;en&#x2F;blog&#x2F;release&#x2F;v8.11.0&#x2F;" rel="nofollow">https:&#x2F;&#x2F;nodejs.org&#x2F;en&#x2F;blog&#x2F;release&#x2F;v8.11.0&#x2F;</a><p>Really hope they&#x27;ll be keeping up-to-date with incremental Node 8 releases, now that they&#x27;ve (almost) caught up with the times.

Have been waiting on this for a very long time. Hopefully AWS will keep up-to-date with LTS versions more quickly in the future. :-)

Looks like this isn&#x27;t available for use with Lambda@Edge&#x2F;CloudFront. Very disappointing :\

New LTS versions of node have been released in September&#x2F;October for the last two years and AWS Lambda has added support for them around April&#x2F;May for the last two years.<p>I wonder if they purposefully wait for x.10 update (6.10 and 8.10) or it has something to do with internal management of projects.