Amazon API Gateway is AWS's managed service for REST, HTTP and WebSocket APIs, billed per call. Pages here cover moving APIs to self-hosted Apache APISIX, Kong Gateway or Tyk for portability and cost.
Comparing Amazon API Gateway with self-hosted Apache APISIX: per-call pricing against running gateway nodes, Lambda and AWS integrations, authentication plugins, caching, and running the same gateway across clouds and data centers.
How the Apache-2.0 Kong Gateway compares with Amazon API Gateway for teams leaving per-call billing: plugins, declarative configuration with decK, database-less mode, which features need Kong's paid editions, and operating it on EKS or elsewhere.
Comparing Amazon API Gateway with self-hosted Tyk: the open source gateway against its licensed dashboard and portal, authentication and quota features, pricing models, and where each runs.
Moving APIs from API Gateway to APISIX: exporting OpenAPI definitions with integration extensions, mapping Lambda, HTTP and VPC link integrations to upstreams, replacing authorizers, usage plans and API keys, and shifting traffic stage by stage.
Rebuilding API Gateway stages as Kong services and routes: converting exported OpenAPI files to declarative configuration, re-creating authorizers with authentication plugins, rate limiting in place of usage plans, and testing before DNS cutover.
Cost of ownership by component: REST, HTTP and WebSocket per-call tiers, caching by the hour and data transfer, against APISIX nodes, etcd, load balancers, monitoring and the people who run them. At what call volume self-hosting pays off.
What API Gateway lets you export: OpenAPI 3.0 or 2.0 definitions per stage, with API Gateway or Postman extensions, the application/json limit on exports, what stays behind such as usage plans, keys and authorizer code, and how to inventory them.
For organizations with APIs in more than one cloud or in their own data centers: replacing API Gateway with one self-hosted gateway, such as APISIX or Kong Gateway, that runs everywhere with the same policies and tooling.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.