Amazon API Gateway Reviews

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. 

We primarily utilize Amazon API Gateway to expose our APIs externally and enhance security by implementing components such as input validation, filtering, and ensuring secure exposure through the gateway.

In our microservices architecture, we utilize Amazon API Gateway. However, since API Gateway doesn't directly support microservice architecture, we require a micro gateway infrastructure. This is why we're exploring alternative API management platforms.

Integrating API Gateway with other AWS services is seamless, especially with cloud-native services like Lambda. It's straightforward to expose APIs built with microservices using Lambda through API Gateway. Additionally, hosting other AWS services as endpoints within API Gateway is convenient.

The performance and scalability of our applications have been impacted by the API database. Managing API scalability is simplified by using API Gateway as a reverse proxy, which centralizes configuration management without requiring developers to modify code frequently. However, for scalability, we primarily rely on AWS's load balancing and autoscaling features rather than API Gateway. Nonetheless, the inherent scalability and manageability of API Gateway as a managed service are beneficial, alleviating concerns about its availability.

One of the most valuable aspects of API Gateway is its native integration with AWS services. This makes it simple to integrate with other services and automate processes within a single script, following a DevOps approach.

We have been utilizing the throttling feature for managing API traffic. With numerous legacy APIs in our system, we've witnessed a significant surge in API requests over time, leading to performance issues due to the lack of throttling. To address this, we require an easier way to adjust throttling settings dynamically as needed.

The authorization and access control features effectively address our security requirements. In terms of API authorization, we rely on OpenID Connect (OIDC), which is not native to AWS but serves our purposes well. User authorization is managed separately for each product platform, with built-in authorization mechanisms tailored to individual products.

API Gateway lacks some usability features that would make it a standard platform for development. For instance, it doesn't include a built-in developer portal, requiring custom development for such functionality. This customization can be extensive and akin to building an entire API management platform from scratch.

The API Gateway lacks the capability to directly facilitate API strategy development or user onboarding workflows. For instance, it doesn't offer out-of-the-box features like developer portals or publisher portals, which are essential for streamlining user onboarding and interaction. These portals play a crucial role in enhancing user adoption by providing a seamless experience for developers and users alike. Currently, API Gateway primarily serves as a technical gateway without built-in support for user engagement functionalities.

I have been working with it for five years.

We serve over a hundred end users across various product areas since our company hosts multiple products. Consequently, we offer distinct API products tailored to each product domain.

We benefit from enterprise support, ensuring prompt responses from the technical support team. I would rate it nine out of ten.

Positive

The initial setup of API Gateway can be somewhat complex, especially if you're unfamiliar with how it operates within AWS. Configuring access control and other aspects like DNS settings can be tricky without prior knowledge of API Gateway and AWS services. Therefore, there's a learning curve associated with setting up API Gateway, which may entail some upfront learning costs.

Deployment time for API Gateway is notably swift. When initiating a new creation within API Gateway, the integration with the DevOps pipeline, especially if all components reside within AWS, ensures a seamless and rapid deployment process. It swiftly establishes the API, sets up the necessary infrastructure, configures the API Gateway, and identifies the requisite DNS for the Gateway endpoints.

I believe the return on investment for API Gateway is satisfactory.

The pricing model for API Gateway is advantageous due to its serverless nature, as it depends on traffic volume. Continuous traffic incurs reasonable costs, as the pricing is based on usage. This flexibility in pricing is appreciated, as it reflects the efficiency of the service provided.

I would recommend API Gateway to those who are uncertain about their API management vision and are already on the AWS platform. It presents an excellent opportunity to start with API management without committing to a specific strategy immediately. Overall, I would rate it six 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.

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.