Amazon API Gateway Reviews

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 Amazon API Gateway to compliment or to put a security facade on top of your current APIs.

It's flexible. It was valuable.

We have not yet explored all of the capabilities. We are looking for a developer portal that may or may not be included, we are not sure.

The integration could be improved.

I have been using Amazon API Gateway for three months. We are using it for a project but it is not in production yet.

There are no issues with the stability of the Amazon API Gateway.

Amazon API Gateway is a scalable solution.

We have integrated into probably eight different areas. We have high volumes. We probably process over 100,000 contracts a day through it.

Amazon has provided us with a dedicated technical advisor. We haven't had any issues with technical support. We're very pleased with it.

There was a bit of a learning curve because we scripted it, but after that it was fine.

We completed the installation ourselves.

Fees are volume-based.

For our current volume, the price is fine, it is what we would expect.

It is doing what we need at this point, there isn't anything extra that we would want.

I would recommend this solution to others who are interested in using it.

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

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.

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.

We are currently using this solution in a project that we are implementing for a public service organization. It is a content management system that will be able to do things like rate monitoring. The service will have good security and availability.

This is a cloud-based deployment with Lambda Integration.

This solution gives you end-to-end protection in what you're able to do. This includes a certificate base, TLS from endpoints, and you can protect the whole link. It will generate certificate keys for you.

This solution gives you a unified way to have your API accessed.

It's a managed product and is fully scalable.

This solution ties in very well with all of the AWS services, such as IAM and asset management. It gives you security from an authentication and authorization point of view.

Lambda integration and functionality is very good.

This solution ties directly in with the AWS firewall, which gives you a lot of security, including application security in terms of things like SQL injection and cross-site scripting.

One of the problems with using this solution is that you have to know a lot about the Amazon ecosystem, in terms of services, to be able to use it. For example, if you use it without the Web Application Firewall then you're going to get some attacks. You have to read the documentation and learn how to use it.

This is a very large product, which means that there is a lot to learn and a lot of documentation to read.

It is not clear to us how you create a direct connection between your on-premises network and the API gateway. In the documentation, it tells you to create a VPN, but I find this troubling at the application level. You should be able to use MTLS. This is what you want rather than direct connect because of security issues. I don't think that this is a documentation issue. Rather, I think that it is a feature that can be improved.

This solution is stable. We will not know for sure until we get into production, but our tests show that stability is fine.

The scalability is excellent, given that it is AWS and not a third-party solution.

We have not fully deployed yet, so we have not had to scale, but scalability is well documented.

I have not contacted technical support personally. Some of my colleagues have, but not about this solution specifically. We do have people that speak with Amazon at times.

The setup of this solution is well documented and examples are provided. I won't say that it is very easy, but you can do it. There are some things that involve creating custom rules, which is not easy. I'm not sure if it can be made easier or not.

We have a good team to handle the implemenation and deployment. Most of our people are pretty technical.

This solution does more for you than a product like Kong.

I have heard complaints that people say this product does not have good security, but that is not true. There is an expectation that you can use it with other Amazon services to provide security, as well as other functionality.

This is a great product. It has ease of use and a full breadth of functionality. I would say that the Amazon platform, in my view, is the best compared to third-party products.

The only real problem is that you have to know a lot about what is outside of the API gateway in order to make the best use of it.

I would rate this solution an eight out of ten.