
AWS API Gateway has become the central entry point for our internal and external APIs, giving us a secure and consistent way to route traffic to multiple backend services. We use it to expose static content from S3, Lambda‑based APIs, and external services running behind ELBs, all governed through a single gateway. Lambda authorizers handle authentication cleanly, and routing based on secret IDs and URL paths makes it easy to manage different workloads without adding operational overhead. Overall, API Gateway ties our architecture together and simplifies how we present a unified API layer across diverse backend systems to customer as one entity backed by Web Application Firewall.
Definitely not an easy service to setup given, if yo use its full potential.
AWS has top notch customer support anyway but debugging will take a lot of time. Review collected by and hosted on G2.com.
Some parts of API Gateway will make stuff overly complex, especially when managing multiple stages, integrations, and custom authorizers (in our case it is Lambda) across different environments along with managing differet API KEYS. Since costs accumulate across requests, caching, and additional features, prediction may not fit well. While it’s powerful, even a small configuration changes sometimes require more steps when so many components are involved. Review collected by and hosted on G2.com.
Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Invitation from G2. This reviewer was not provided any incentive by G2 for completing this review.




