Support for tagging of Lambda functions and for the Python 3.6 runtime

Re:Support for tagging of Lambda functions and for the Pytho... by southpolesteve on Tuesday April 18, 2017 @07:53PM (#14144202)

API Gateway needs less config since they released the proxy style integration. In Lambda's case this means you can just return a JSON object like:

{ "statusCode": 200, headers: {}, body: "<h1>Hello!</h1>" }

And API Gateway knows exactly what to do. Before this, yes there was some extra config and it was not fun.

PS. Our AWS bill went down when we moved everything to Lambda but that was not the motivating factor for the switch

[ Parent | on HN ]

Re:Support for tagging of Lambda functions and for the Pytho... by takeda on Tuesday April 18, 2017 @09:14PM (#14144646)

Is it possible that perhaps your EC2 instances were bigger than they should be, and perhaps to make Lambda work in satisfactory manner you also placed CloudFront in front of it?

Because those sites you mentioned (bustle.com and romper.com) look like something that could benefit a great deal from using CDN which would then drastically reduce need for large instances.

[ Parent | on HN ]