Amazon API Gateway Reviews

I use API Gateway to trigger Lambda functions, manage S3 objects, and direct traffic for my web applications. Everything I use is integrated with the API Gateway.

API Gateway has simplified integrating different AWS services for deploying applications, providing a streamlined approach.

The Cognito authorization integration is very useful, along with the easy multi-region integration and connectivity with various AWS services like SQS, SNS, and Lambda functions.

API Gateway could be more user-friendly, especially in defining routes for new users. A friend of mine had difficulty with understanding where the API Gateway stages were and whether they were deployed. An interface more friendly for new users would be helpful.

I have been using AWS services for a long time, possibly ten years.

I do not remember any issues or problems with the stability.

I did not use a different solution before API Gateway. Implementing an API outside AWS is more challenging, so API Gateway has made things much easier for me.

It is a really cheap product, but if used incorrectly, it can become expensive. Balancing your charges is crucial to control the costs.

I'd rate the solution ten 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.

I use it to expose API. So, I primarily use it for publishing our APIs and implementing rate limiting.

We mainly use it within our internal services.

It eliminates the need for us to handle rate limiting ourselves.

It completely met our expectations. We have no issues with it.

Moreover,  integrating API Gateway with other AWS services was good. It worked out of the box, so it worked perfectly.

We heavily utilize AWS Cognito user pools and application authorization responses for authentication and authorization.

A lower price would definitely be an improvement. 

I would like to see more AI-based capabilities in future releases. 

I have been using it for more than three years. 

I would rate the stability an eight out of ten. 

I would rate the scalability an eight out of ten. We have thousands of end users accessing our solution built on API Gateway. Internally, around 100 people are involved in development.

We use it daily. 

The customer service and support are great.

Positive

I would rate my experience with the initial setup an eight out of ten, with ten being easy.

The deployment took a few minutes. 

The deployment was done in-house. One DevOps engineer is enough for the process. 

We don't need to maintain the solution. It just works. It does not require any maintenance. 

I would rate the pricing a five out of ten, with ten being expensive. 

We evaluated Microsoft Azure. We did a comparison. We decided to use all services from Amazon, like database deployment, etcetera. It was logical to continue using Amazon API Gateway because it fits better.

Overall, I would rate the solution an eight out of ten. 

Our use case is we have some internal APIs that we need to expose to the outside world. Via API Gateway, we expose those APIs to the external world.

It is easy for integrations if it is deployed in AWS Services.

The setup is very simple. 

It is stable and reliable.

It can scale well.

We would like to see more UI-based monitoring.

I've been using API Gateway for around six months.

It's a stable, reliable product. There are no bugs or glitches. It doesn't crash or freeze. 

We can scale the product. it's not a problem if we need to expand it. 

The solution was just recently deployed. We have about 1,000 new users on it. When were are fully operational, we will have about 10,000 users on the solution. We are still in the process of expanding usage. 

We've never had to reach out to technical support. Therefore, I cannot speak to how helpful or responsive they are. 

We also use Apigee from Google. 

We didn't switch from anything. This was a new requirement. Since all of our components are in AWS, we took the AWS API Gateway solution to make it easy for integration for all other AWS components.

The solution offers an easy initial setup. 

It takes two weeks to deploy the solution. 

We only need about two individuals to handle any maintenance tasks. We may need up to six people once we are fully up and running. We'll need one manager, two administrators, and two people for support.

We did the implementation in-house. We did not need outside assistance from consultants or integrators. We had people on our team that could do it.

We did evaluate other options before choosing this solution. 

I'd recommend the solution to other users and companies. If you are using AWS components, then it is a good product.

I'd rate the product eight out of ten.

We are integrating the Amazon API Gateway for one of our projects in phase four. We also use our built-in agent assist system to connect the customer to the backend. It handles and processes API calls for the application's responses.

Amazon API Gateway facilitates our serverless architecture, particularly with Lambda, by allowing us to perform various tasks. For instance, Lambda functions authorize API calls, execute multiple workloads, and integrate with other services like Azure and Kubernetes. Additionally, we leverage Lambda functions behind the Amazon API Gateway to query databases, process data, and interact with different systems.

The tool's most valuable aspect is its scalability. It empowers us to expose endpoints internally or externally, adapt to various requirements such as rate limiting, and ensure security measures for API utilization.

The tool's UI requires time to understand. 

I have been using the product for eight to nine years. 

The tool is stable. I've deployed it for a client with millions of users without issues.

The solution's scalability has improved the performance and reliability of our API. Being a fully managed service, it offers auto-scalability and management by AWS. Amazon API Gateway is scalable. My company has more than 1000 users. 

Whenever we require support from Amazon, they respond promptly.

The tool's deployment is straightforward. It sometimes takes a little more time to understand the UI, but it's pretty easy to use once you grasp it properly. We rely on automation to set it up. 

We did not use a consultant or an integrator. We handled all the work in-house, including authenticating and setting up the architecture. 

I think it's one of the best API management solutions I've used. I've previously worked with other API management tools but prefer the Amazon API Gateway. I rate it a ten out of ten. 

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. 

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