Amazon API Gateway Reviews

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.

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 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 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.