Amazon API Gateway Reviews

We use it for normal API purposes.

Its security feature is the most valuable because it is mainly a security solution. It has easy authentication and authorization, and its integration is also useful.

The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface.

I have been using this solution for more or less one year.

Its stability is great.

It is very scalable because it is in the cloud. We might have around ten thousand users of this solution. The client for whom we deployed this solution is using this solution and won't be changing it or increasing its usage in the near future.

I haven't really used technical support. Its documentation is really good and complete. There are a lot of things on the website that you can use.

We didn't have a different solution. 

It is ready to be used because it is in the cloud. It is very straightforward to set it up with some support. The deployment duration depends on the number of services, but generally, it takes around two hours.

We used an in-house resource. In terms of maintenance, we have a team that supervises not only this product but also other products. I think the product itself doesn't require much monitoring or maintenance. It is really managed by the cloud.

We didn't evaluate other options because our environment is in Amazon, so it didn't make sense to use another solution.

This is a good solution for anyone whose strategy is to run entirely on Amazon. You basically have to use another approach if that's not the case. If you have a hybrid cloud or if you are trying to be independent of the cloud, this is not a good solution for you. 

I would rate Amazon API Gateway an eight out of ten. It is a complete solution.

We primarily use this solution for exposing internal data sources to the internet.

The ability to proxy has been the most valuable feature.

The pricing could be better. Also, possibly better technical support services or possibly just more documentation to assist users.

The scalability is very good. We plan to slowly increase usage. We have a number of things we need to do with it. It won't grow substantially, but maybe to double what we've done so far.

Like most Amazon services, and this one's the same, you're expected to effectively do your own support, and any other support is by emails, so it's quite limited.

We didn't previously use a different solution.

The initial setup is pretty easy. Deployment only takes five minutes.

We are an integrator, so we did the implementation ourselves.

We've not yet directly seen any ROI, but we weren't expecting to.

The pricing can always get better, but it's pretty reasonable and it's a pay as you go model.

We evaluated Dell Boomi and we looked at Informatica.

The user interface is easy enough to use. I don't really have any complaints about it. In terms of advice for implementing and using, I would say you should make sure you've got good internal skills.

I would rate this solution 8 out of 10.

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.

We use it for API routing and managing traffic. These are managed authentications between the API and back to primary users. 

Our services are deployed only in AWS Cloud. It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway. I'm going to continue using it for my projects. A few of the projects are deployed in Amazon, some in GCP, but most are on the AWS.

I am not completely satisfied with Technical Support. They were finding it difficult to get to the AWS API gateway. Also, the traffic percentage was not calculating correctly.

I have used Amazon API gateway for a year or so. We use a Hybrid version.

It's very stable. I'm satisfied with that.

I'm satisfied.

I am not completely satisfied with Technical Support.

It's straightforward. It took 15 minutes to deploy.

We implemented this in-house. 

We compared Google APIG to the Amazon APIG. The Google APIG is more for the open banking APIWSA2. The Google APIG are more advanced in terms of the open banking API compared to the AWS API gateway.

I recommend it for open banking. I would rate it 8 out of 10. To get to 10 it would It would need more support for open banking, via the open API. If your existing workloads are in AWS, then you can surely go for the AWS Amazon, AWS API gateway. If it is a hybrid solution, then I would suggest you go for WSA2. Konghybrid GCP is also good.

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.

We primarily use the solution for providing controlled access to our services running within Amazon.

You can code anything and hook it on to it but it doesn't give you stuff out of the box like the other gateways give you. You can do anything with it because you just attach a LAN to it and it will do anything, but that's to the custodian. You know you're not using the power of the gateway. It's hard to configure. There's a lot of options but it's very hard, it's very confusing.

In the future, I'd like to see Amazon develop a portal and monetization that is not only for the Amazon Marketplace.

The solution is very stable.

The solution is very easily scalable.

The technical support is very strong. We've had issues with the solution and configuration and we've gotten very good support.

We used something else, but Amazon is more powerful. We moved to the cloud.

I didn't do the initial setup, so I'm not sure how hard it was to implement, or how long deployment took. Right now, we have two DevOps people handling the maintenance.

We didn't evaluate any other options before choosing this current solution.

I would rate this solution a five out of 10. If there was a better configuration, I'd give it a higher score.

We use the solution to protect APIs from malicious attacks.

The solution's performance and scalability could be better than Azure.

We have been using the solution for two years.

The solution is stable.

The solution is scalable.

Comparatively, Azure is better than AWS in terms of performance and scalability.

The solution's initial setup process is straightforward.

The solution's price is reasonable.

I rate the solution a nine out of ten.