Amazon API Gateway Reviews

We primarily use the solution as an API gateway. The APIs are managed by serverless applications. It's an API gateway from Layer 7.

The integration with Comdata is very good.

The product is affordable.

It is easy to set up. It is also quick to deploy.

The solution is reliable. It is very stable. 

The solution can scale well. 

The solution could improve signature validation. They should offer signature validation if there is any request. There needs to be some sort of mechanism. They need to be able to validate the signature at the API gateway level. 

I've used the solution for about three years. 

The solution is stable and reliable. There are no bugs or glitches. There are no improvements needed. The performance is good. 

The solution is scalable. There's no problem if we need to expand. We have around 600 APIs working right now. We have plans to increase usage in the future. 

I did not use any other solution previously.

There are multiple ways to set up the solution. It's very simple and straightforward. 

The deployment shouldn't take too long, depending on the requirements. We can do it in just a minute. The work is very minimal. 

First, we set up the routes and set them up with the network, and in terms of integration, if there are any authentications needed, we do that as well. 

We do not need many staff members to handle deployment and maintenance. 

We can handle the setup ourselves. It's very easy.

We've seen value in using the solution. It is worth the money. 

The licensing is paid monthly. It's a minimal charge. It is very affordable. There are no extra costs. 

We did not evaluate other options. 

I am an end-user.

I've been using the latest version of the solution. 

I highly recommend the product. 

I'd rate the product ten 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 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 clients have specific use cases. They require a gateway that performs well and can handle around three hundred requests per quarter.

It provides the flexibility to configure, switch, and manage configurations through cloud permissions or performance settings. This includes services such as cloud monitoring tools, user connections, and the essential components required for API services. The gateway, in conjunction with other interconnected services, facilitates smooth operations. It covers aspects like cloud monitoring, user authentication through cloud sign-ins, and more. In my experience, as a service that we use extensively, it acts as a master tool, offering easy configuration and excellent integration capabilities with third-party services.

It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end. Their support services come at a considerable cost, leaving room for improvement.

I have been working with it for over five years.

The stability is highly guaranteed, as AWS itself provides the cloud service with a reliability of 99.99%. This translates to a maximum of two hours of downtime annually, making it an exceptionally stable platform. I would rate it nine out of ten.

I would rate the scalability nine out of ten. I haven't observed any significant issues indicating a lack of scalability, as it can be efficiently managed through configurations. Our clientele primarily consists of enterprise customers.

Although they deliver high-quality services, the technical support comes at a significant cost. I would rate it six out of ten.

Neutral

The initial setup is somewhat complex and I would rate it seven out of ten. The main challenges stem from the intricacies of subnets and the overall plan in place.

The deployment time is contingent on the other services we provide, the features we utilize, and the consultants involved. The duration of this process is influenced by the integration aspects, typically spanning just a few weeks. We deploy using the POC process, adapting specifics to client preferences and performance needs. Clients can choose Docker, Kubernetes, or Amazon API Gateway based on their interests and infrastructure requirements.

I would rate its pricing six out of ten.

Opting for the cloud is a swift decision, and once made, the process proceeds smoothly. The consensus is positive, with no apparent reluctance. However, a crucial point is the necessity for expertise, particularly in AWS. Without the right proficiency, the implementation might not proceed seamlessly. Overall, I would rate it eight 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 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. 

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