News for hackers. Stuff that matters.
Re:New for AWS Lambda – Environment Variables and Serverless... by aleem on Sunday November 20, 2016 @01:57PM (#13000442)
It works remarkably well if you use a development toolchain (serverless and claudia are both good though I prefer the latter).

My only gripe is that API Gateway (APIG) charges $3.5 per million requests and there is no other way to invoke lambda functions over HTTP. Had to scale back my micro-service ambitions because of this.

Re:New for AWS Lambda – Environment Variables and Serverless... by hayd on Sunday November 20, 2016 @03:29PM (#13000996)
Hmmmm, I know it seems ridiculous but I wonder if it would it be cheaper to just spool up an ec2 machine and async invoke the lambda call e.g. via boto?

It seems like APIG has a boat load of features, which is great... but they are mostly unused.

Re:New for AWS Lambda – Environment Variables and Serverless... by hayd on Sunday November 20, 2016 @08:05PM (#13002322)
potentially I'm looking for something like this (to proxy_pass to a lambda function with nginx) https://github.com/washingtonpost/nginx-aws-lambda
Re:New for AWS Lambda – Environment Variables and Serverless... by realcoopernurse on Sunday November 20, 2016 @08:13PM (#13002352)
I wrote a AWS Lambda plugin for the Caddy web server which can take the place of API Gateway.

https://caddyserver.com/docs/awslambda