Amazon API Gateway Reviews

When you have multiple API applications, Amazon API Gateway can serve as both your front end and your middleware. When you have microservices, for example, you can run Amazon API Gateway with Kubernetes. It can also build out the requests.

We also have the serverless application being hosted in Lambda. Lambda is an AWS resource that we use Amazon API Gateway with when we have received a request. It redirects the traffic to that particular request.

It's a brilliant service.

It is very helpful, with our API-based applications. As a service that is provided by Amazon, you do not need to maintain it or, monitor the traffic, you can simply configure it and it is ready to use.

Amazon API Gateway is secure, you can have the WAF rules, base protected. In terms of security, you can always have WAF rules, it's good.

When it comes to integration, it is currently integrated with CloudWatch monitoring. As a result, monitoring the APIs to external servers is not an option. This is a feature that should be added, similar to what we have for ServiceManager.

Monitoring could be improved.

I have been using Amazon API Gateway for three years.

Amazon API Gateway does not require scaling. We can easily add certain rules.

You can update, and deploy it at any time. They have a zero content deployment strategy in place. 

We have many different applications with this solution. We have approximately 30 to 40 applications that use this solution.

I have raised some tickets with concerns or issues that we have experienced and they have been quick to respond. We have full support from AWS. The technical support is very good.

The installation is straightforward. It can be done through the command line or just by using the UI. 

The documentation provided by Amazon is wonderful. You just follow the steps and you can easily get started with it.

We have used it through Terraform, we created the scripts, opened the pathways, and configured them. Once the script is ready, it can be applied. This process is not an issue and can be done in two to three minutes. 

When it is being done through the UI, you have all of the configurations in mind, and it doesn't require a lot of time to set up. When the setup is ready, you just have to apply. It does not require a lot of time overall.

We have a technical team and a development team who work on creating the New APIs. They are very familiar with this solution. One person who is very familiar and one other maintain this solution. At times, we have a team of three or four people who have experience with AWS to deploy, maintain, and create the configurations.

There are no licensing fees.

It is the most recommended solution to use.

What I have explored is limited. I am not sure if any other external integrations are required. To my knowledge, they already integrate with other services. We are pleased with what we have.

I would definitely recommend this solution for microservices-based applications. For example, if they are using a Lambda function that is serverless, you will want to move the Lambda functions to the API gateway it is recommended. 

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

I use the solution in my company for microservices architecture. I have five years of experience with Amazon and Tenable. I see many services offered by Amazon.

The product's high price is an area of concern where improvements are required.

I have been using Amazon API Gateway for three years.

It is a stable solution.

It is a scalable solution. My company uses the autoscaling features of the product.

Sometimes, my company contacts technical support for solutions. The technical support team is very quick to respond to our company.

The product's deployment phase was easy, especially if you use Terraform, which can help automate the deployment process.

The product is expensive.

Speaking about how Amazon API Gateway has facilitated cloud application integration, I use the tool since I want to look at the microservices it offers. I use many of the microservices offered by the product, along with Kubernetes and Lambda.

In terms of securing APIs, I can handle a lot of services on the desktop and also manage the load-balancing part.

My company uses the dashboards provided by the product for API monitoring.

I recommend the product to those who plan to use it.

I recommend the product because it offers many microservices for infrastructures. It can be deployed quickly. The tool can be very expensive. The product is strong when it comes to its autoscaling features and Lambda-related functionalities.

I rate the tool a seven out of ten.

We put the APIs behind an API gateway. Before the users hit the API, they must go through the Amazon API Gateway. We can control how people use our APIs. We use the tool to manage the entire API process.

Building an API gateway is not a simple process. It is good to use a managed service that is cost-effective. The solution is solid, robust, and scalable. It gets the job done.

We faced a few issues with the documentation. We had to figure out many things on our own, or we had to watch some videos. It would have been much easier if the documentation were a little clearer.

I have been using the solution for three years.

The tool is very stable.

All the employees who deploy applications use the product in our organization. We have about 100 users.

The tool is cloud-based. We have to configure it. It is not difficult. The configuration is straightforward. Everybody can do it. I rate the ease of setting up authorization and authentication mechanisms a seven out of ten.

The solution is worth the money.

The product is a little expensive. It's not free. However, the tool's cost is better than the cost of setting up our own gateway. It could be cheaper, though.

Amazon API Gateway is a solid service. Considering the cost of setting up an API gateway, it’s best to use Amazon API Gateway. Overall, I rate the tool an eight out of ten.

We integrated Amazon API Gateway with their microservices architecture using GitHub and Java.

They could include more support tools in the product.

We have been using Amazon API Gateway for 1 year.

I rate the platform's stability an eight.

My team has around 18 to 20 Amazon API Gateway users. We use it frequently, twice a day, to stay connected. I rate the scalability a seven or eight out of ten.

We encountered challenges accessing technical support channels, such as a need for a clear telephone number and chat sessions. The PIN verification is time-consuming, often resulting in chat sessions expiring and requiring them to reconnect repeatedly.

Neutral

The setup usually takes a few hours to complete depending on the client's requirements. I rate the initial setup process a six out of ten.

A consultant facilitated the setup.

I rate the platform's pricing a five out of ten.

I couldn't recommend the product as it is an on-premise solution, and everyone is shifting the environment to the cloud infrastructure.

I rate it an eight out of ten.

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.

I use this solution for mobile app development. It is the API gateway for my backend.

The most valuable feature is the ease of managing the gateway.

This solution is useful for making new APIs. We deploy with CloudFormation, so it's pretty easy to use.

The way they manage the headers could be improved and made easier.

There are some certificates that they will not let us use.

I would like to see the web console improved.

There should be more videos and documentation about the new features that are released every month.

This solution is very stable.

It is a scalable solution. We have ten users in my team who service approximately five thousand people through our apps, and we are increasing the usage every day.

We have a solution architect from AWS and he is working with us. The support from Amazon is great. On a scale of one to five, I would rate technical support a five.

We did not use another cloud solution prior to this one. However, we did use an on-premises API gateway from CA Technologies. It is a very capable solution, but it is more expensive and we also had to maintain it ourselves. It is not a managed service like the API gateway from AWS.

The initial setup of this solution is very easy. It only takes a few minutes.

This solution is a managed service, so we don't need to be concerned with maintenance. AWS does the management and scaling for us. It's serverless.

I took care of the deployment myself.

We have seen ROI. It's pay-per-use, so you won't lose any money.

This is a pay-per-use service, where you only pay for what you use.

We had our on-premises solution, and we also evaluated Apigee from Google. Ultimately, we felt that AWS, for our use case, was the best option. The main reasons are the ease of use and pricing.

My advice to anybody who is implementing this solution is to first read the documentation and follow the steps. Make a use case, create a proof of concept, and then migrate it to production environments. It's pretty easy to use.

This is a good product, but there is always room for improvement.

I would rate this solution an eight out of ten.

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.