EU alternative · Amazon API Gateway

European alternative to Amazon API Gateway

Public HTTP, WebSocket, and prefix routes are entries in gateway.routes. Each route has a name, a type, and a target. API Gateway stages, models, and authorizers are not imported.

What you declare on the gateway

An HTTP route targets a function, a worker, or an inference endpoint. A WebSocket route targets a function. A prefix route targets a bucket and can serve a static site. The route name is the stable id reviewers see in kernstack plan.

Custom hostnames are attached on the route. Redirects from one host to another are listed beside the routes. The same project holds the function or bucket the route calls, so the path and the code are reviewed together.

What stays behind in API Gateway

An API Gateway REST or HTTP API is not parsed. Stages, deployments, request validators, mapping templates, usage plans, and Lambda authorizers do not become fields on the route.

You write the route you want. You do not paste an exported OpenAPI document from API Gateway and expect KERNSTACK to keep those extensions. A person accepts the plan diff before the route is public.

Amazon API Gateway vs KERNSTACK on European Bare Metal

Dimension Amazon API Gateway KERNSTACK Gateway
Operator AWS account KERNSTACK project
Manifest Amazon API Gateway console or API gateway.routes
Region AWS region list European bare metal
Bill Amazon API Gateway line item One project credit balance

Frequently asked questions

No. You add routes under gateway.routes. Stages, models, mapping templates, and authorizers are not copied.

HTTP, WebSocket, and prefix. HTTP and prefix can target the resource named in the route. WebSocket routes target a function.

kernstack plan prints the route diff. A person accepts it before the hostname serves the new target.

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.