AWS pushed out the docs for this new feature but then quickly pulled them down. Likely it will be announced during re:invent coming up.<p>The original doc url (taken down now) was: https://docs.aws.amazon.com/lambda/latest/dg/invocation-urls.html<p>Google has a cache here: https://webcache.googleusercontent.com/search?q=cache:Qr4xUaiHjAsJ:https://docs.aws.amazon.com/lambda/latest/dg/invocation-urls.html+&cd=1&hl=en&ct=clnk&gl=us
Yes, I posted this yesterday ( <a href="https://news.ycombinator.com/item?id=29285371" rel="nofollow">https://news.ycombinator.com/item?id=29285371</a> ) but then it was taken down.<p>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.
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).
This came out three days ago already. Apparently a premature launch, but it’s still in the changelog of the AWS JS SDK: <a href="https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md" rel="nofollow">https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md</a>