Prompt
I hate using AWS API Gateway for managing lots of APIs
Latest observation
Oct 5, 2026
OpenAI APIWeb search: off
That’s a pretty common reaction. API Gateway can get painful when you have lots of APIs, especially if you’re dealing with:
- many routes/endpoints
- repeated auth/config boilerplate
- stage/deployment complexity
- versioning and environment sprawl
- mapping templates, throttling, and custom domains
- awkward local testing and slower iteration
If you want, I can help in a few directions:
-
Vent / compare alternatives
We can talk through what specifically sucks about API Gateway and what tools are better depending on your setup. -
Suggest better architectures
For example:- ALB + containers/Lambda
- CloudFront + Lambda@Edge / Functions
- Kong / Tyk / Envoy / NGINX as an API gateway layer
- BFF pattern to reduce API sprawl
- GraphQL if you’re really managing many related endpoints
-
Help optimize API Gateway usage
If you’re stuck with AWS, I can suggest ways to make it less awful:- OpenAPI-first workflows
- IaC with Terraform/CDK/SAM
- centralized authorizers
- route grouping conventions
- deployment automation
- per-service API design patterns
If you tell me:
- how many APIs/routes you have,
- whether they’re REST or HTTP APIs,
- whether backend is Lambda, ECS, EKS, or something else,
- and what part you hate most,
…I can recommend the least annoying option.