Amazon API Gateway Reviews

All of my APIs and microservices are behind the Amazon API Gateway. When someone sends a request to the API Gateway, it performs validation and then forwards it to the appropriate microservice. Several microservices, such as payment services, deposit services, and account services, are all behind the API Gateway.

For me, there are many valuable features. The solution is a managed service and requires minimal configuration, which makes it easy to launch an API. Moreover, there is support for analytics and configuration options for volume, security, rate limits, and more.

I would like to improve the restrictions and security elements of the solution, as there are certain configurations that are not currently supported. There are certain restrictions that cannot be implemented without web access.

In the next release, I would like a feature that can validate requests and filter out any jQuery injections. Additionally, I would like to prioritize these requests. I've noticed that such features are usually not available in web applications.

I have been using Amazon API Gateway for three years.

It is a stable solution.

It is a scalable solution. Although, scalability depends on the type of APIs being deployed, security, and the market.

For example, it depends on the type of APIs being deployed and the volume of calls to the APIs. The number of concurrent users also impacts scalability. Our company has around 4,000 to 5,000 concurrent users per year and sometimes up to 10,000 to 15,000. However, I haven't tested the scalability of the API Gateway for that volume of calls.

The support team is good.

The initial setup is straightforward. It took only a day to deploy the solution. You can do it with the help of documentation, anyone can easily configure the setup.

The ROI of Amazon API Gateway depends on the type of API being deployed. If you are monetizing your API, then the calculation is different. However, if you are using the API gateway for your own business services, you should consider the ROI in terms of the cost of developing a similar service on your own. This way, you can determine if the investment in the API gateway is worth it. If the cost of developing the service on your own is higher than the cost of using the API gateway, then the ROI will be great.

The licensing model is based on the number of pay calls made. It was not expensive.

We primarily use the solution as an API gateway. The APIs are managed by serverless applications. It's an API gateway from Layer 7.

The integration with Comdata is very good.

The product is affordable.

It is easy to set up. It is also quick to deploy.

The solution is reliable. It is very stable. 

The solution can scale well. 

The solution could improve signature validation. They should offer signature validation if there is any request. There needs to be some sort of mechanism. They need to be able to validate the signature at the API gateway level. 

I've used the solution for about three years. 

The solution is stable and reliable. There are no bugs or glitches. There are no improvements needed. The performance is good. 

The solution is scalable. There's no problem if we need to expand. We have around 600 APIs working right now. We have plans to increase usage in the future. 

I did not use any other solution previously.

There are multiple ways to set up the solution. It's very simple and straightforward. 

The deployment shouldn't take too long, depending on the requirements. We can do it in just a minute. The work is very minimal. 

First, we set up the routes and set them up with the network, and in terms of integration, if there are any authentications needed, we do that as well. 

We do not need many staff members to handle deployment and maintenance. 

We can handle the setup ourselves. It's very easy.

We've seen value in using the solution. It is worth the money. 

The licensing is paid monthly. It's a minimal charge. It is very affordable. There are no extra costs. 

We did not evaluate other options. 

I am an end-user.

I've been using the latest version of the solution. 

I highly recommend the product. 

I'd rate the product ten out of ten. 

Our primary use case is a fully serverless architecture for the application.

The most valuable feature is it has lots of integration.

When it comes to  DDoS protection, I would like to see that become available at the API Gateway level.

I have been working with Amazon API Gateway for the past two years.

There is excellent stability.

The scalability is currently showing me ten thousand requests per second. That is very good in our case.

The initial setup is straightforward and easy.

The deployment has taken us around eighteen minutes to complete.

We use all open-source technology.

I would rate Amazon API Gateway a nine out of ten.

We're using Amazon API Gateway for API management.

What I like best about Amazon API Gateway is that it's simple to use, easy to set up, and you can quickly get it up and running. It's a very user-friendly solution.

I also didn't experience any issues in terms of Amazon API Gateway interface, integration, or monitoring. The solution runs smoothly.

Currently, I'm not facing any issues with Amazon API Gateway, which satisfies my requirements. I'm pretty happy with what Amazon API Gateway offers, but as its pricing is on the higher side, that's one area for improvement in the solution.

What I'd like to see in the next release of Amazon API Gateway is an improvement in the status checks you get from the monitoring feature of the solution. Currently, you get the number of requests received, the number of reports, etc., but if there are more details than what's given by Amazon API Gateway, that will improve the solution.

I've been using Amazon API Gateway for around a year.

Amazon API Gateway is a very stable solution.

Amazon API Gateway is a scalable solution.

Support for Amazon API Gateway is quite good. The support team is knowledgeable. I interacted with the support team only once, as it's a pretty stable solution, so I don't need much support, but the interaction I had with the team was professional.

On a scale of one to five, I'd rate overall support for Amazon API Gateway as four.

The initial setup for Amazon API Gateway was easy. I would rate it as five on a scale of one to five.

Amazon API Gateway has various pricing plans, but I cannot give the exact cost, though I can say that it's expensive. On a scale of one to five, I'd rate the pricing for Amazon API Gateway as two, as the solution is one of the most expensive products in the market for API management.

My company has around three to four team members who use Amazon API Gateway, but the solution is also being used by many clients who connect to it and consume APIs.

Amazon API Gateway is being used daily.

I advise anyone looking into using Amazon API Gateway to go ahead and use the solution. Still, you should consider your load requirements and what you're looking for in a solution before making that decision.

My rating for Amazon API Gateway is nine out of ten.

I'm a customer of Amazon API Gateway.

Our use case is we have some internal APIs that we need to expose to the outside world. Via API Gateway, we expose those APIs to the external world.

It is easy for integrations if it is deployed in AWS Services.

The setup is very simple. 

It is stable and reliable.

It can scale well.

We would like to see more UI-based monitoring.

I've been using API Gateway for around six months.

It's a stable, reliable product. There are no bugs or glitches. It doesn't crash or freeze. 

We can scale the product. it's not a problem if we need to expand it. 

The solution was just recently deployed. We have about 1,000 new users on it. When were are fully operational, we will have about 10,000 users on the solution. We are still in the process of expanding usage. 

We've never had to reach out to technical support. Therefore, I cannot speak to how helpful or responsive they are. 

We also use Apigee from Google. 

We didn't switch from anything. This was a new requirement. Since all of our components are in AWS, we took the AWS API Gateway solution to make it easy for integration for all other AWS components.

The solution offers an easy initial setup. 

It takes two weeks to deploy the solution. 

We only need about two individuals to handle any maintenance tasks. We may need up to six people once we are fully up and running. We'll need one manager, two administrators, and two people for support.

We did the implementation in-house. We did not need outside assistance from consultants or integrators. We had people on our team that could do it.

We did evaluate other options before choosing this solution. 

I'd recommend the solution to other users and companies. If you are using AWS components, then it is a good product.

I'd rate the product eight out of ten.

The most valuable feature in Amazon API Gateway is the itinerary release.

Amazon API Gateway can improve the user interface in some areas it could be more polished.

In a future release, it would be beneficial for more documentation, even though their documentation is already very good, but better documentation could help us build more of what you want yourself.

I have been using Amazon API Gateway for approximately seven months.

I have not reached out to the support from Amazon API Gateway.

The initial setup of Amazon API Gateway is straightforward and the process took approximately one day.

We did the implementation of the solution in-house.

There is an annual licensing cost to use Amazon API Gateway.

My advice to others would be for them to keep their eye on the cost.

I rate Amazon API Gateway a nine out of ten.

The gateway is the first layer of protection. When traffic comes in, we need to complete a couple of validation steps such as adding a rate limit. We then scan documents for viruses and upload them. All information and data needs to be sanitized before it enters a private domain and we use this solution to do this.

The most valuable feature of this solution is the SQL injection.

The UI and UX of this solution could be improved. From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution. 

We have been using this solution for two years. 

This is a stable solution. 

This is a scalable solution. 

A lot of learning materials are available and it is easier than it used to be to use. Previously you needed to pay for support. 

Neutral

The initial setup is straightforward. From security perspective, it takes time to get everything approved. 

Huawei has their own version of API Gateway, which is equivalent or better than AWS in some cases. It is pre integrated with standard security features.

The suitability of this solution depends on an organization's use case and architecture.

I would rate this solution an eight out of ten. 

We use an API from Amazon to assess our internal services in our VPC and to limit the access of certain users to API and to have an execution plan. Certain users have certain access to API calls that they could use to give them an assessed quota.

The solution is deployed on a private cloud.

Amazon stack is easy to use in combination with other Amazon services, so it was a logical continuity. We use Amazon Lambda, so using Amazon API Gateway is the logical continuity of the same step. It wouldn't be very practical to use technology from Azure because we are already using Amazon.

The user interface could be improved, as well as customer support and having a local customer representative in a country. Monitoring could also be improved a bit.

I have been using this solution for one year.

The solution is stable so far.

It is scalable.

I haven't had a case where I needed to talk to a local representative, but as an overall problem for sales, that is something that could be improved.

We usually find answers on the internet or through other materials.

The solution was easy to set up. I did the setup by myself.

I am satisfied with the price.

We evaluated other options like Microsoft. They are very similar, but because of our customers, they insist on using Amazon.

I would rate this solution 8 out of 10.

If you get used to a certain technology, you would definitely recommend it to your customer because you have experience. We recommend this technology to our customers because we are using it for other products and we have experience, and then the core learning or integration course is shorter.