Amazon API Gateway Reviews

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.

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.

The solution is user-friendly. 

The course management needs improvement. It's always an issue to set up the course management, especially when you use data form. We use a lot of TerraForm scripts to build up our environment. The rest is pretty straightforward and pretty easy to use.

I have experience with Amazon API Gateway.

The scalability is good. There are one hundred thousand users using it in our company. I rate the overall solution a ten out of ten. 

The initial setup is not easy as it includes a lot of steps. 

Overall, the solution is a nine out of ten. 

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.

I use AWS API Management and Mulesoft because I work on different solutions and I am in a different layer, because I most focused on backend solutions. I have participated in some projects using these tools but I am not a developer or an expert.

We have designed and implemented RESTful API's. For example, based on Microservices with Spring Boot and AKS or OpenShift.

In terms of the most valuable features, it would say that it is really easy to start working with it.

I'm fine with the interface. It's okay. I think it also is really useful with the pay per-use. The cost is interesting.

It would be useful to have a more complete development environment for the developer, with different integrative capabilities to manage all the life cycles for the API. I think the full version formula for that is really useful. They should improve the development environment for easier integration.

I have been using Amazon API Gateway for about one year.

It is stable. I haven't find many issues in the program, so I think it's a stable.

We have many teams working on the solution, between 10 and 50, and there are between 8 and 10 people per team.

The initial setup is easy because you don't have to install anything. It's cloud. It is in a base mode, so to start working with that the setup is really easy.

I was looking for information regarding AWS API gateway and MuleSoft because I am looking for some different arguments to put on the table for a comparative for a customer. In my opinion MuleSoft is a tool that lets you to manage all the life cycles for the API. I think it's a more complete solution. In AWS you don't have the capabilities to manage all the life cycle for the API's. Also you don't have other capabilities for implementing different integration patterns. I think that's the main difference that I found between these tools.

The advice that I would give others regarding Amazon API is that it depends on the use cases. If they have a complex environment, they need to consider different integration patterns. It could be that AWS Management is not enough for them. They would have to compliment it with another solution. It is really working in some cases, but you do need to evaluate all the requirements to choose the tool. If you are working only in the AWS context with different services or something like that, it's really useful to work with AWS Management.

On a scale of one to ten I would rate Amazon API Gateway an eight.

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.

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.