an HTTP(S) frontend for Lambda Functions • A [reverse] proxy for other HTTP(S) endpoints ◦ Rate limiting (e.g. legacy endpoints) ◦ Adding authentication and CW Metrics • To invoke AWS Services directly without a compute component
Gateway as it should have been since the beginning” ~anonymous Has only the most useful* functionality of API Gateway: • Can act as an HTTP(S) proxy for Lambda Functions • Can act as a [reverse] proxy for other HTTP(S) endpoints • Easy authentication and authorization via JWT
HTTP APIs: • Cheaper: $ 1.11 vs $ 3.50 per million requests • No backend caching (not serverless!!!!!!) • Authentication via JWT • Easier CORS • Easier deployments (and shorter URLs) • Faster due to less service overhead, in some cases + 1 million free invocations