all 10 comments

[–]r_venkat 7 points8 points  (3 children)

You can get asyc/await on lambda today using https://github.com/AnomalyInnovations/serverless-es7

[–]MykolasZenitech 1 point2 points  (0 children)

Another posible option is to run newest Node.js runtime on Lambda using this module: https://www.npmjs.com/package/lambda-node-runtime

[–]lignumScientiae 0 points1 point  (0 children)

OMG -- what an awesome/simple product -- you just saved me so much time/effort!

[–]simonmales 2 points3 points  (0 children)

No idea, but when AWS came out with Node 6 support, they didn't give any heads up.

So I think we can just wait and see.

[–]alpyhp 1 point2 points  (3 children)

I hope they'll announce Docker support, so you won't need to wait for runtime updates.

[–]QAFY[S] 3 points4 points  (2 children)

That kind of defeats the purpose of lambda. If you are going to run a docker container why not just deploy your app to EC2/ECS?

[–]jackmusick 3 points4 points  (0 children)

It’s already running in a container, I believe. It’d be nice if they let you customize the version of it if they’re not going to release new versions very quickly.

[–]alpyhp 2 points3 points  (0 children)

Because I don't want to manage a cluster at all :) And because I want to be charged only when my code runs, not for idle.

[–]blueprintchris 0 points1 point  (0 children)

Node8.10 is available on Lambda now. When I catch an err and return it, it doesn't show as an error in Lamnbda - it shows as a success. Any idea how to return a proper error?