Was waiting for this update! Running Puppeteer related projects will now be a ton easier for ad hoc project.<p>I'm pretty deep into this with <a href="https://checklyhq.com" rel="nofollow">https://checklyhq.com</a> so not really an "ad hoc" user. Some open concerns for "real" 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/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's obsolete for my business.
This is massive for AWS Lambda (and we've waited a long time for this). We can now use async/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's also not yet listed in the docs: <a href="https://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunction.html#SSS-CreateFunction-request-Runtime" rel="nofollow">https://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunct...</a><p>Or perhaps it's not available in all regions yet?
Perhaps this will make headless chromium easier<p><a href="https://www.npmjs.com/package/@browserless/aws-lambda-chrome" rel="nofollow">https://www.npmjs.com/package/@browserless/aws-lambda-chrome</a>
This update was a very long time coming, so I'm grateful that it finally happened.<p>Still, it's disappointing that they couldn't change course (ever so slightly!) to accommodate the 8.11.0 <i>security update</i> from a week ago: <a href="https://nodejs.org/en/blog/release/v8.11.0/" rel="nofollow">https://nodejs.org/en/blog/release/v8.11.0/</a><p>Really hope they'll be keeping up-to-date with incremental Node 8 releases, now that they've (almost) caught up with the times.
New LTS versions of node have been released in September/October for the last two years and AWS Lambda has added support for them around April/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.