If I take into consideration the past three to four years, during which I used the tool, I would say that some missing and external configurations were not possible in the product, and it was a bit difficult to manage.
Amazon API Gateway stands out for its seamless integration with AWS, ease of use, scalability, and support for secure API management, benefiting from a serverless architecture that helps control costs while ensuring efficient backend connectivity.
| Author info | Rating | Review Summary |
|---|---|---|
| Programmer at Ministry of Interior | 4.0 | In my experience, managing Amazon API Gateway has been challenging due to missing and external configurations that were not possible, especially over the last few years. |

If I take into consideration the past three to four years, during which I used the tool, I would say that some missing and external configurations were not possible in the product, and it was a bit difficult to manage.
I have been using Amazon API Gateway for more than five years. I am an implementer of the tool. I am a solution architect, specifically an enterprise architect whose role is to provide the best solution for organizations based on their requirements.
Stability-wise, I rate the solution a seven or eight out of ten.
Scalability-wise, I rate the solution a seven out of ten.
My company's clients consist of medium-sized businesses that are looking for a solution.
Considering the time zone differences, there were times when my company had to wait for a day to get a response from the support team. I rate the technical support an eight out of ten.
Positive
The product's initial setup phase was difficult.
There was one more team in my company that was involved with AWS and the DevOps team, who were used to struggling with the product's initial setup process. As a solution architect, I found the product's initial setup process difficult.
The solution is deployed on a public cloud.
If you just take into consideration the application part during the setup process, it can be managed in minutes.
The product can be described as a medium-priced solution, but its cost is higher than Azure.
I am involved in the process of integrating Amazon API Gateway with microservices architecture.
I use REST for Amazon API Gateway.
Speaking about how Amazon API Gateway's caching feature has an impact on API performance, I would say that my company has its own caching mechanism written in Java. Even in AWS, our company uses a caching feature.
In terms of the product's authorization and access control features, I would say that there is a component in AWS that we can use. Among the three projects my company handles, for one of the projects, we used LDAP for authorization. In one of the projects handled by our company, we have used AWS as a component.
All the features of the product are good, but it all depends on the end users who need to accept the solution. If you you ask me, the cloud solutions are very good, irrespective of whether users go for AWS, Azure, or GCP.
Considering the monitoring and analytics feature in Amazon API Gateway, I would say that my company used the tool for analytics along with Microsoft, which we recently used for Spring Boot Actuator since it provides production-ready features, including health check metrics. My company also uses a third-party API for analytics purposes.
The monitoring and analytics feature in Amazon API Gateway was the reason I implemented microservices on AWS in some of my earlier projects with a different company. Presently, I work for the Ministry of Interior of Qatar, and we now want to move to microservices. I was involved in doing some research to figure out whether to choose Spring Boot or MicroProfile, an open-source service for microservices.
The product is really good when it comes to API lifecycle management, and it is not just something that includes the balancing part or the security aspect but also the routing and the fallback mechanism.
I recommend the product to those who plan to use it. When you go for a cloud solution, the main advantage is that users can choose not to have an infrastructure, where they may have to opt for a pay-as-you-go model. For small and medium-sized organizations, AWS, Azure, or GCP are fine. In my case, since I have an extensive database, I think it is good to go with Amazon API Gateway.
I rate the solution an eight out of ten.
| Product | Mindshare (%) |
|---|---|
| Amazon API Gateway | 7.5% |
| Microsoft Azure API Management | 10.3% |
| Apigee | 6.8% |
| Other | 75.4% |
| Company Size | Count |
|---|---|
| Small Business | 12 |
| Midsize Enterprise | 10 |
| Large Enterprise | 19 |
| Company Size | Count |
|---|---|
| Small Business | 241 |
| Midsize Enterprise | 96 |
| Large Enterprise | 359 |
Amazon API Gateway offers significant capabilities for managing APIs, integrating smoothly with AWS Lambda for serverless operations. It provides robust security with authentication, authorization, and input validation. The gateway supports API traffic management, rate limiting, and enhances accessibility while facing areas for potential improvements in pricing, documentation, interface usability, monitoring, security, latency, analytics, and debugging tools. Expanded integration features and AI-based development aids are desirable.
What features make Amazon API Gateway effective?Amazon API Gateway is frequently employed in industries like mobile development and public services to ensure secure, efficient interactions between front-end and back-end systems. It's instrumental in managing APIs, integrating microservices, and offering controlled API access, notably in environments requiring robust security and service exposure.
Autodesk, Fox Digital Consumer Group, iFlix, UK Driver and Vehicle Licensing Agency (DVLA), Miovision, Olympusat, PhotoVogue, Royale International Group, Veracode