Yes, I posted this yesterday ( https://news.ycombinator.com/item?id=29285371 ) but then it was taken down.

Very exciting as I just spent a few hours cobbling together the cloudformation for a simple API gateway -> Node lambda. The lambda just calls a few AWS APIs. Cutting out the API gateway will be a plus.

I am contrast like the API Gateway side of things. Not sure how they'll manage custom domains in that kind of thing but we have a bunch of APIs hosted by ECS lambda and direct S3 endpoints.

Also we have a custom lambda authorizer that protects most of our endpoints. Also with multi-file swagger support, setting up the swagger file for API gateway is a breeze.

As someone who uses the serverless framework to abstract this can anyone tell me why they don't like the API Gateway? I'm sure there are valid reasons, I've just not run into any issues wiring up my lambdas with the API Gateway (using serverless, I've never done it manually).

Fantastic! Using api-gateway for this was so annoying.

Nice, I recently tested out SAM for a webhook I deployed which was quite smooth, but this is definitely a step in the right direction.

This came out three days ago already. Apparently a premature launch, but it’s still in the changelog of the AWS JS SDK: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md

I can't tell from the page. Does it have support OAuth natively?