Try our new research platform with insights from 80,000+ expert users
Solution Architect at EPAM Systems
Real User
Top 5Leaderboard
The solution excels in simplifying the process of building endpoints swiftly
Pros and Cons
  • "API Gateway offers a multitude of configuration parameters that enable versatile request filtering and protection against potential attacks."
  • "When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions."

What is our primary use case?

I've primarily used the solution to call Lambda functions and embrace new features that they introduce. My role doesn't require me to explore the full range of API Gateway features, but rather simpler ones like repair gateway functions as and when required. Additionally, in relation to AWS Step Functions, there are key distinctions between instant and long-life step functions that should be highlighted. It isn’t very transparent and useful for me. Instant step functions are suitable for tasks that can be completed within around ten minutes, whereas long-lived ones can endure for extended periods by saving their states between steps.

What is most valuable?

API Gateway offers a multitude of configuration parameters that enable versatile request filtering and protection against potential attacks. It's possible to customize settings based on the specific needs of the application. Additionally, API Gateway supports integration with various technologies.

Covering all the functions is difficult due to the extensive range, but it excels in simplifying the process of building endpoints swiftly.

What needs improvement?

When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions. This has led me to devise shortcuts that aren't entirely straightforward but serve my needs.

It's important to consider the type of gateway endpoint carefully. There appear to be two distinct types. It's crucial to make an informed selection based on your project's requirements. When utilizing API Gateway, the choices one makes regarding endpoint types and properties are pivotal. After initially choosing an endpoint type, it is difficult to switch to a different type later on.

For how long have I used the solution?

I have been using Amazon API Gateway for five years. 

Buyer's Guide
Amazon API Gateway
February 2025
Learn what your peers think about Amazon API Gateway. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
832,138 professionals have used our research since 2012.

What do I think about the stability of the solution?

I would rate the stability a ten out of ten. However, one interesting point is that Amazon claims to have a step functions engine that can be executed not only in the cloud but also on your personal laptop or on-premises environments. This usage is intended for testing and development rather than production purposes. Although I haven't personally utilized it, I'm interested in this feature which can expand the market for Amazon's solution and offers an interesting avenue for evaluation.

What do I think about the scalability of the solution?

It is highly scalable. I rate the scalability a ten out of ten. 

How are customer service and support?

API Gateway's technical support is good. Many common cases are already covered through guides and resources. I haven't personally encountered an issue requiring assistance, I am aware that they are responsive when asked for support.

How was the initial setup?

The initial setup is straightforward. It is a service that Amazon provides. There are three types of configurations; Web UI, Command Line Control, and Plug-in. The command line control allows you to set and configure a gateway. The plugin allows you to fine-tune API Gateway settings and manage various endpoints directly.

What about the implementation team?

API Gateway is an Amazon service that doesn't require deployment on the local workstation. Using WebUI, you configure settings, click "deploy," and the changes are stored on Amazon's storage, taking only a few seconds for the changes to take effect. Unlike traditional deployment, you're not creating binary files. Instead, you're adjusting configuration settings.

There is no team needed for deployment, however, a software architect is needed for the configuration.

What other advice do I have?

I would recommend the solution to others. You should consider using API Gateway when working with other Amazon cloud components like Amazon RD, Amazon storage, or AWS Lambda for serverless computing. It has its own value separately but API Gateway is interconnected with the broader Amazon service ecosystem. I would overall rate it an eight out of ten. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Prasanth MG - PeerSpot reviewer
Software Engineer at Readyly
Real User
Top 5Leaderboard
Has efficient scalability and robust authentication features
Pros and Cons
  • "It is a stable solution."
  • "Its support for SAM integration could be made more accessible."

What is our primary use case?

We use the solution as a gateway between the front-end and the back-end. It helps us setup proper authentication and provides a neat and easily configurable view of our application's public interface.

How has it helped my organization?

We decided to connect our Lambda functions to the solution. Its authentication feature helps us secure the APIs.

What is most valuable?

The solution has the best scalability. We can add as many endpoints as required. Also, we can authenticate using API keys and Lambda authorizers. In addition, there are three types of gateways, HTTP, Rest API, and Web Sockets. Out of them, Rest API provides robust and more secure authentication features whereas Web Sockets enable two-way communication which is helpful to implement a chat application.

What needs improvement?

The solution's configuration for API gateways using SAM and CloudFormation templates could be more accessible.

For how long have I used the solution?

We have been using the solution for more than a year.

What do I think about the stability of the solution?

It is a stable solution. However, sometimes it takes a minute to respond after the first deployment. But, once it starts, it never fails.

What do I think about the scalability of the solution?

It is a scalable solution. We have five users in our organization.

How was the initial setup?

The solution's initial setup process is easy.

What other advice do I have?

I rate the solution a ten out of ten.

I advise others to use Lambda authorizer instead of API key-based authorization for more secure keys. It will help them use different tokens per customer.

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Amazon API Gateway
February 2025
Learn what your peers think about Amazon API Gateway. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
832,138 professionals have used our research since 2012.
reviewer1652133 - PeerSpot reviewer
Cloud Engineer at a retailer with 10,001+ employees
Real User
Secure, easy to use, includes WAF rules, has responsive technical support, and provides excellent documentation
Pros and Cons
  • "It is very helpful, with our API-based applications."
  • "Monitoring could be improved."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Amazon API Gateway for three years.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

There are no licensing fees.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
AnkurGupta7 - PeerSpot reviewer
Technical Architect at Evon Technologies Pvt
Real User
Top 10
Comes with auto-scalability features but UI require time to understand
Pros and Cons
  • "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 UI requires time to understand."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

The tool's UI requires time to understand. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

How are customer service and support?

Whenever we require support from Amazon, they respond promptly.

How was the initial setup?

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. 

What about the implementation team?

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

What other advice do I have?

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. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Serg Anonymous - PeerSpot reviewer
Project Manager at Yukon
Real User
Top 5
Met our expectations and eliminates the need for us to handle rate limiting ourselves
Pros and Cons
  • "Integrating API Gateway with other AWS services was easy. It worked out of the box, so it worked perfectly."
  • "A lower price would definitely be an improvement."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

A lower price would definitely be an improvement. 

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

For how long have I used the solution?

I have been using it for more than three years. 

What do I think about the stability of the solution?

I would rate the stability an eight out of ten. 

What do I think about the scalability of the solution?

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. 

How are customer service and support?

The customer service and support are great.

How would you rate customer service and support?

Positive

How was the initial setup?

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

The deployment took a few minutes. 

What about the implementation team?

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. 

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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.

What other advice do I have?

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

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Deputy Manager - Radio Frequency Planning at RF-SMART
Real User
Top 5Leaderboard
A stable solution with an exceptional uptime
Pros and Cons
  • "The most valuable feature of the solution is that it is a stable solution with an uptime of 99.99 percent."
  • "Amazon API Gateway needs to focus on minimizing latency."

What is our primary use case?

I use the solution for API management. I use Amazon API Gateway for SQL Server Stretch Database.

What is most valuable?

The most valuable feature of the solution is that it is a stable solution with an uptime of 99.99 percent.

What needs improvement?

Amazon API Gateway is expensive, making it one of the product's shortcomings where improvements are required.

Amazon API Gateway needs to focus on minimizing latency.

For how long have I used the solution?

I have been using Amazon API Gateway for a year.

What do I think about the stability of the solution?

Stability-wise, I rate the solution a nine out of ten.

What do I think about the scalability of the solution?

It is a scalable solution. Scalability-wise, I rate the solution a nine out of ten.

Around ten employees in my company use the solution.

Considering that my organization is closed as of now, I can't comment on whether there are plans to increase the use of the solution in the company.

How are customer service and support?

I have experience with the solution's technical support.

Which solution did I use previously and why did I switch?

Apart from the cloud services offered by Amazon and Google, our company has not used any other products.

How was the initial setup?

The product's initial setup phase was not complex.

At first, my company needed to deal with Amazon's authentication requirements, after which we put all our information in Amazon API Gateway. Then, we run the setup file and add the attribute data before we can finally operate it in our company.

The solution is deployed on the cloud.

The solution can be deployed in two hours.

Five technicians are sufficient to take care of the deployment and maintenance of the product.

What about the implementation team?

My company sought an integrator's help to carry out the product's installation process.

What's my experience with pricing, setup cost, and licensing?

The solution is expensive. Though the product was previously available at a cheap rate, nowadays it is expensive.

What other advice do I have?

Amazon is the number one cloud service provider in the world.

I recommend the solution to others since it is a good product.

The benefit that I have experienced from using the solution stems from the fact that it is a secure and reliable product to use.

I rate the overall product a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Daniel Boadzie - PeerSpot reviewer
Machine Learning Specialist at Hubtel
Real User
Top 10
A stable, robust, and scalable solution that can be configured easily
Pros and Cons
  • "The solution is solid, robust, and scalable."
  • "We faced a few issues with the documentation."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using the solution for three years.

What do I think about the stability of the solution?

The tool is very stable.

What do I think about the scalability of the solution?

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

How was the initial setup?

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.

What was our ROI?

The solution is worth the money.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Atal Upadhyay - PeerSpot reviewer
AVP at MIDDAY INFOMEDIA LIMITED
Real User
Top 5Leaderboard
Highly stable solution that provides good management features
Pros and Cons
  • "It allows us to expose our APIs and provides tools for managing them."
  • "I believe better governance and monitoring features would be beneficial."

What is our primary use case?

So we are using Amazon API Gateway in our application. It allows us to expose our APIs and provides tools for managing them.

What needs improvement?

As for improvements, I haven't fully explored Amazon API Gateway yet, but I believe better governance and monitoring features would be beneficial.

We are also interested in telemetry, analytics, and other features that are important for our API management. I would appreciate more comprehensive telemetry information, diagnostics, and improved monitoring capabilities for the services and endpoints.

For how long have I used the solution?

We have been using Amazon API Gateway for more than a year or two. We are using the latest version.

What do I think about the stability of the solution?

It is a stable solution. I would rate the stability an eight out of ten. It has been working quite well so far. 

What do I think about the scalability of the solution?

There are over thousand users in our organization using this solution. So, I would say it is a scalable solution. 

Which solution did I use previously and why did I switch?

We currently have most of the features we need. However, we are evaluating different commercial options and considering reaching out to MuleSoft and Kong for further discussions.

How was the initial setup?

The initial setup is straightforward. It's not overly complex. Setting up Amazon API Gateway is fairly easy, and most of our requirements are well supported by the platform.

We have an in-house team to maintain the solution. 

Which other solutions did I evaluate?

I have worked with various API gateways. For example, I have experience with the Azure API gateway and also the AWS API gateway. However, we are currently planning to migrate to an enterprise-level solution, so we are evaluating MuleSoft's Telecom API.

The simple API setup is good enough for us, but we are looking for more advanced features in enterprise-level API management. We are planning to transition to a different API gateway.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Amazon API Gateway Report and get advice and tips from experienced pros sharing their opinions.
Updated: February 2025
Product Categories
API Management
Buyer's Guide
Download our free Amazon API Gateway Report and get advice and tips from experienced pros sharing their opinions.