Prompt
Unhappy with AWS API Gateway complexity
Latest observation
Oct 23, 2026
OpenAI APIWeb search: off
If you’re unhappy with AWS API Gateway complexity, that’s a pretty common feeling. It’s powerful, but for many use cases it can feel heavy, confusing, and full of knobs you don’t actually need.
A few practical alternatives, depending on what you’re trying to do:
Simpler AWS-native options
- Application Load Balancer + Lambda / ECS / EC2
- Good if you mainly need HTTP routing and don’t need full API management features.
- Lambda Function URLs
- Very simple for exposing a Lambda over HTTPS.
- Best for lightweight internal tools, prototypes, or simple public endpoints.
- App Runner
- Easier than API Gateway + Lambda if you already have a small web service.
- CloudFront + Lambda@Edge / origin
- Useful for edge routing, though not a direct API Gateway replacement.
Non-AWS API gateways / ingress layers
- Kong
- NGINX
- Traefik
- Tyk
- KrakenD
- Envoy
These can be much more straightforward if you want:
- custom routing
- auth
- rate limiting
- request/response transforms
- lower operational surprise than API Gateway
If your goal is just “make APIs easier”
You might simplify your architecture by:
- using Lambda Function URLs instead of API Gateway
- putting ALB in front of services
- moving to a framework that generates OpenAPI docs automatically
- using a lightweight gateway only where needed, not everywhere
Rule of thumb
- Need full managed API features, throttling, auth, stages, caching? API Gateway may still be worth it.
- Need simple HTTPS endpoints? You probably want something lighter.
If you want, I can help you pick a replacement based on your setup:
- Lambda-only
- ECS / containers
- Kubernetes
- Public API
- Internal API
- Mostly just simple HTTP routing