Amazon API Gateway Reviews

My use case for Amazon API Gateway involves using it for backend APIs and mostly private API Gateways. We utilize it within the context of a microservices architecture. The front-end technology connects through the API Gateway to backend services running on Lambda, making the API Gateway an endpoint for reaching backend services.

Amazon API Gateway provides easy scalability and fast deployment, making it less time-consuming to spin up services. Its serverless technology allows our applications to scale seamlessly according to demand.

A most valuable feature of Amazon API Gateway is how quickly we can connect to backend services and have APIs accessible from anywhere. This flexibility supports our operations efficiently.

I'd appreciate improvements in the user interface to make it more understandable, especially for new AWS users. Documentation can be confusing at times, so more details on the connection between the API Gateway and backend services would be helpful. Additionally, a local version of the API Gateway would be beneficial for testing purposes without incurring extra costs.

I have been using Amazon API Gateway for almost two and a half years now.

Amazon API Gateway has proven to be very stable, with a stability rating of ten out of ten. The high stability ensures that we do not encounter workflow issues, which is critical for maintaining uninterrupted operations.

Regarding scalability, I would rate Amazon API Gateway at eight out of ten. Although we have not faced challenges, we have not tested scalability on a large scale either. In our typical use cases, scalability aligns with our expectations and requirements.

The support from AWS was adequate when we needed assistance, particularly during the setup of a private API Gateway. There was initial difficulty due to unclear documentation, but the AWS team's help was effective, even though it took some time to get the correct answers.

Neutral

The initial setup was moderately complex; I would rate it a six out of ten. Understanding the service's intricacies and integration with Lambda was the major challenge initially, but it became easier over time.

The deployment process typically involves only one person, which is myself. Maintenance does not require many people due to its serverless nature.

The pricing of Amazon API Gateway is cost-effective unless there is a very high volume of requests. I would rate the pricing as reasonable, giving it a score of five out of ten.

For newcomers to Amazon API Gateway, it's advisable to watch a few AWS videos to grasp how it works. The documentation can be difficult to follow initially, so supplementing it with external learning resources can provide a better understanding.

I'd rate the solution seven out of ten.

If I take into consideration the past three to four years, during which I used the tool, I would say that some missing and external configurations were not possible in the product, and it was a bit difficult to manage.

I have been using Amazon API Gateway for more than five years. I am an implementer of the tool. I am a solution architect, specifically an enterprise architect whose role is to provide the best solution for organizations based on their requirements.

Stability-wise, I rate the solution a seven or eight out of ten.

Scalability-wise, I rate the solution a seven out of ten.

My company's clients consist of medium-sized businesses that are looking for a solution.

Considering the time zone differences, there were times when my company had to wait for a day to get a response from the support team. I rate the technical support an eight out of ten.

Positive

The product's initial setup phase was difficult.

There was one more team in my company that was involved with AWS and the DevOps team, who were used to struggling with the product's initial setup process. As a solution architect, I found the product's initial setup process difficult.

The solution is deployed on a public cloud.

If you just take into consideration the application part during the setup process, it can be managed in minutes.

The product can be described as a medium-priced solution, but its cost is higher than Azure.

I am involved in the process of integrating Amazon API Gateway with microservices architecture.

I use REST for Amazon API Gateway.

Speaking about how Amazon API Gateway's caching feature has an impact on API performance, I would say that my company has its own caching mechanism written in Java. Even in AWS, our company uses a caching feature.

In terms of the product's authorization and access control features, I would say that there is a component in AWS that we can use. Among the three projects my company handles, for one of the projects, we used LDAP for authorization. In one of the projects handled by our company, we have used AWS as a component.

All the features of the product are good, but it all depends on the end users who need to accept the solution. If you you ask me, the cloud solutions are very good, irrespective of whether users go for AWS, Azure, or GCP.

Considering the monitoring and analytics feature in Amazon API Gateway, I would say that my company used the tool for analytics along with Microsoft, which we recently used for Spring Boot Actuator since it provides production-ready features, including health check metrics. My company also uses a third-party API for analytics purposes.

The monitoring and analytics feature in Amazon API Gateway was the reason I implemented microservices on AWS in some of my earlier projects with a different company. Presently, I work for the Ministry of Interior of Qatar, and we now want to move to microservices. I was involved in doing some research to figure out whether to choose Spring Boot or MicroProfile, an open-source service for microservices.

The product is really good when it comes to API lifecycle management, and it is not just something that includes the balancing part or the security aspect but also the routing and the fallback mechanism.

I recommend the product to those who plan to use it. When you go for a cloud solution, the main advantage is that users can choose not to have an infrastructure, where they may have to opt for a pay-as-you-go model. For small and medium-sized organizations, AWS, Azure, or GCP are fine. In my case, since I have an extensive database, I think it is good to go with Amazon API Gateway.

I rate the solution an eight out of ten.

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.

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.

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.

I have been using Amazon API Gateway for five years. 

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.

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

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.

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.

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.

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. 

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.

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

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.

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

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

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

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

The solution's initial setup process is easy.

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.

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

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

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

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.

I have been using Amazon API Gateway for a year.

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

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.

I have experience with the solution's technical support.

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

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.

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

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

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.

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

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.

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

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

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

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.

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. 

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.

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