Amazon API Gateway Reviews

We use Amazon API Gateway for some solutions we have integrated with ServiceNow. Some operations need to be done with the help of Amazon API Gateway. If API Gateway's path is available, we can easily integrate it with other solutions.

Amazon API Gateway is a very fast solution.

The solution has a major limitation compared to Google Cloud. Amazon API Gateway will wait for only 30 seconds to get a response from other services, such as the Lambda function. API Gateway can be directly integrated with the Lambda function, and a response from the Lambda function must be obtained within 30 seconds.

I have been using Amazon API Gateway for five years.

I am satisfied with the solution’s stability.

We are using the solution for three to four projects by big clients.

I am satisfied with the solution’s technical support.

It is easy to install because we use a third-party tool called Serverless to define the Amazon API Gateway path. We are integrating the API gateway with the Lambda proxy on the back end. All the things are written in the Serverless file in YAML format. We are using Serverless to deploy on the cloud automatically.

All authentication mechanisms, like the access key and secret key, can be configured in the corresponding machine. It will then be authenticated against the access key and security key, and it will be automatically deployed on that particular account.

The solution's pricing is cheap and based on the number of requests coming to Amazon API Gateway.

Since the deployment should be automatic, it's better to use the Serverless tool to deploy the solution. Otherwise, you can use Terraform. Manually creating something will be a problem. It is easy for somebody to learn to use API Gateway for the first time. When we integrate Amazon API Gateway with any other service like Lambda, there will be a log associated with it, which you can find out.

Overall, I 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.

I use Amazon API Gateway for student data management of microservices to share between other systems. The solution is used between different applications in our organization. Amazon API Gateway is used along with Salesforce, Oracle, ServiceNow and SQL solutions. 

The simplicity of use is one of the vital features of Amazon API Gateway. It's a low-code solution that helps our company manage operations seamlessly. 

The solution should include change data capture (CDC) features that will help reduce workload. The aforementioned feature can be introduced as a mini plug-in or additional license. 

 In future versions of the product, there can be automated integration capabilities for applications through AI. 

I have been using Amazon API Gateway since 2016. 

Amazon API Gateway is a highly stable solution. 

At our company, we had some issues with scaling initially, but that was resolved soon enough. Amazon API Gateway exhibits satisfying scalability. Our organization never faced any issues with the performance and scalability of the solution. The first two or three weeks post-adoption, we had some learning issues in the company. After fine-tuning certain aspects and updating the query optimization in the solution, we never faced any issues in our company. 

As our company had to migrate from a Microsoft environment and remove Informatica as the middleware, the introduction of microservices and the initial setup process were a bit difficult. In our company, it took us initially a month to setup the environment and configure the code for Amazon API Gateway.

After the solution was deployed into the CI/CD pipeline, we fine-tuned it in our company for a year. This was necessary because new applications and processes were added. 

Presently, our company team is experienced enough to deploy the solution in one or two days. When we first installed the solution around 2015 in our organization, there wasn't much information available about the product or the setup process. After deploying Amazon API Gateway, our company does not need to maintain the solution.

Our company website uses most of the data coming through the solution, so there are more than 200,000 end users of the solution per month. Some portions of the total data arrive from the backend systems and other additional applications, such as student services.

There are 35,000 students connected to our company, so they can be considered as end users of the solution too. Overall, I would say there are more than 400,000 users of Amazon API Gateway in our organization through mobile app access. 

Our company is able to realize an ROI using Amazon API Gateway for application management. 

Azure products are more cost-effective than AWS solutions. 

AWS is the pioneer for gateway solutions. But with tools like Azure API Management and Azure Active Directory, Microsoft has been able to gain a lot of traction, AWS needs to gain an edge with additional features to beat Microsoft as a competitor. In my company, Azure products are used much more than AWS solutions. I have witnessed, in recent times, large companies migrate towards Azure from AWS. 

For API management, the serverless Lambda in the tool is the most used feature from Amazon API Gateway. The aforementioned feature is quite easy to use and integrate in a minimal team structure and no knowledge of Dot.Net and SQL is required. Using the Lambda feature, our company team could develop certain services within two weeks. 

Authorization and access control features of Amazon API Gateway meet the security needs of our organization. At our organization, we needed to make some customizations such as both-end encryption for data security. The environment and provisioning capabilities are already present in a simplified format in Amazon API Gateway.

I would definitely recommend Amazon API Gateway to other users, I am able to design solutions completely using the tool. Some organizations don't prefer to work with multi-vendor products, and some customers might be already too habituated to the Azure environment products such as Azure Dynamics and ERP solutions due to the extensive features. I would overall rate Amazon API Gateway a nine out of ten. 

We use Amazon API Gateway to expose our back end to the front end.

The best thing about Amazon API Gateway is that it can authenticate and authorize requests without going to our back end. We can use the solution to authenticate a request. It has a time out of 30 seconds, wherein it will show time out if any request takes more than 30 seconds.

We can create many sub-resources in a single resource. Instead of creating five resources for five APIs, we can create five sub-resources in only one resource. I love working with Amazon API Gateway because it is very user-friendly.

I faced issues with the timeout because some machine-learning scripts would take more than 30 seconds. Since the first invocation of AWS Lambda takes more than 30 seconds because of Lambda's cold start, Amazon API Gateway blocks that resource, thereby aborting the invocation.

I have been using Amazon API Gateway for two years.

Amazon API Gateway is a highly stable product.

More than ten people are using the solution in our organization.

The solution’s technical support is good.

Amazon API Gateway is a very cheaply priced product.

It is very easy for a beginner to learn to use Amazon API Gateway and to create some resources manually. You can download one CDK script to create that same resource in any other environment a second time.

Amazon API Gateway is a serverless product. We don't need to manage servers. We only need to create the resources that we need to create. It is a completely deployed product. We create our AWS account, and we can create APIs directly. We don't need to worry about servers.

Setting up the authorization and authentication mechanism with Amazon API Gateway is very easy and takes only half an hour. We are actively migrating from on-premises to AWS or any other cloud. We will have a very big use case for Amazon API Gateway in the future.

You should be very specific with the configuration if you are a new user. Initially, you should have a very simple configuration and not use a proxy. If you have a use case to expose the Amazon API gateway to any front-end resources, you have to allow CORS and set headers. Be specific with the headers and CORS configuration, and don't make it complex. Don't jump directly into advanced configuration.

Overall, I rate the solution a nine 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.

All of my APIs and microservices are behind the Amazon API Gateway. When someone sends a request to the API Gateway, it performs validation and then forwards it to the appropriate microservice. Several microservices, such as payment services, deposit services, and account services, are all behind the API Gateway.

For me, there are many valuable features. The solution is a managed service and requires minimal configuration, which makes it easy to launch an API. Moreover, there is support for analytics and configuration options for volume, security, rate limits, and more.

I would like to improve the restrictions and security elements of the solution, as there are certain configurations that are not currently supported. There are certain restrictions that cannot be implemented without web access.

In the next release, I would like a feature that can validate requests and filter out any jQuery injections. Additionally, I would like to prioritize these requests. I've noticed that such features are usually not available in web applications.

I have been using Amazon API Gateway for three years.

It is a stable solution.

It is a scalable solution. Although, scalability depends on the type of APIs being deployed, security, and the market.

For example, it depends on the type of APIs being deployed and the volume of calls to the APIs. The number of concurrent users also impacts scalability. Our company has around 4,000 to 5,000 concurrent users per year and sometimes up to 10,000 to 15,000. However, I haven't tested the scalability of the API Gateway for that volume of calls.

The support team is good.

The initial setup is straightforward. It took only a day to deploy the solution. You can do it with the help of documentation, anyone can easily configure the setup.

The ROI of Amazon API Gateway depends on the type of API being deployed. If you are monetizing your API, then the calculation is different. However, if you are using the API gateway for your own business services, you should consider the ROI in terms of the cost of developing a similar service on your own. This way, you can determine if the investment in the API gateway is worth it. If the cost of developing the service on your own is higher than the cost of using the API gateway, then the ROI will be great.

The licensing model is based on the number of pay calls made. It was not expensive.

We mainly use these APIs for east-to-west communication within our internal system and partner collaboration. While most companies prefer tool-based API management for partner collaboration, for internal consumption, and integration between application insight, we tend to use cloud-native tools provided by AWS.

The most valuable features are the standard ones that APIs offer. Depending on the requirements, Azure API management's throttling feature is used for continuous consumption. Otherwise, we rely on the default features available. 

Since it is mainly for internal communication, we haven't received any concerns or requests for better tools or additional features. The initial tools provided by Amazon API Gateway suffice for our needs.

The only issue we've noticed is a lack of awareness when it comes to partner collaboration. Customers prefer using separate API gateways for scalability. Apart from that, feature-wise, most API management solutions offer similar features and learning resources on how to use them.

The pricing could be improved. In cases where customers require real-time sync or real-time calling groups with IoT, the volume of data and time lag become a concern. AWS charges for data ingress and egress, which could be further reduced. This would be helpful for customers dealing with large amounts of data coming in or going out from their systems. So, improving pricing for volume data transfer is something that can be considered, as it has been consistent feedback from customers.

It has been around four years since it became publicly available. We have tier-one partnerships with all the hyperscalers, including AWS, Azure, and GCP. 

It is a stable solution. I would rate the stability a nine out of ten.

I would rate the scalability a nine out of ten. It is very scalable, and we don't need to hire additional engineers.

Our clients are primarily enterprise businesses. We have a strong customer base in log integrations.

The support is good, especially if you are a premium partner with AWS or have active scalable support. If you have a tier-one partnership, the support has been phenomenal. 

However, if the partnership is lower, it may take more time or have SLAs involved. But overall, the support team is more receptive than the infrastructure team. 

Positive

Currently, we mainly focus on cloud-native solutions. We have a couple of partnerships, including Dell Boomi and MuleSoft. We also had a customer requirement for Apigee design, so I was looking for a comparison between API management with cloud-native tools and their offerings. 

Generally, we recommend using API management provided by the Hyperscale industry, such as AWS, Azure, and GCP Virtual Desktop.

The initial setup is straightforward. With big data forms and CI/CD automation, it becomes very straightforward.

Most of the time, we have seen hybrid and cloud deployments being preferred by our customers. That has been the dominant use case for most of them.

The Amazon configuration IT process usually takes a couple of hours. If the requirements are clear and there are no additional requests from the customer's side, it's just a matter of a couple of hours to set up the new components for straightforward and simple requirements.

The pricing can be expensive depending on the use case. If there is a lot of data processing involved, it can become a costly solution. However, it is still better than other products available in the market. Since our customers are mostly large enterprises, they prefer not to go for open-source alternatives or cheaper limited services. They prefer to stick with what is available with the Hyperscale providers.

We use API tools from Amazon, Azure, and sometimes GCP depending on where the customer workloads are. For Azure, we use Azure EDP management, and for Amazon, we use generative VPN management. Most of our requirements revolve around Azure APM management and AWS APM engine.

The features we look at are mostly similar across the board. There aren't many differentiating factors. For example, in terms of orchestration, Azure offers step functions or Lambda functions, which are available in AWS as well. 

The customers tend to use the native features unless they need to work with different API gateways for scalability reasons. The only issue we've noticed is a lack of awareness when it comes to partner collaboration. Customers prefer using separate API gateways for scalability. Apart from that, feature-wise, most API management solutions offer similar features and learning resources on how to use them.

We would definitely recommend sticking to native solutions because then you have one Hyperscale provider supporting the applications, storage, compute, and APIs. 

Another aspect to consider is the security features within the API. If you need to collaborate outside the organization, there are numerous security features available through the Hyperscale provider that can be leveraged. 

However, if there is a very specific requirement that the native API Gateway doesn't fulfill, then you can explore other external products or solutions.

Overall, I would rate the solution a nine out of ten.

We use Amazon API Gateway to expose some APIs. I worked for three companies that mostly used API Gateway for exposed services and complex use cases like expose headers. The solution is used to personalize responses, provide more simulations, and facilitate communication between the services. The solution is also used to direct some requests to Lambda and ECS.

Amazon API Gateway can integrate with ECS and Lambda. With Amazon API Gateway, you can have massive integrations that are quickly integrated.

Amazon API Gateway is not as complete as Apigee and needs to be improved by adding more features to become a more robust application.

For some use cases, Apigee is more complete than Amazon API Gateway. With Apigee, you can integrate some endpoints with better latency. Apigee has the cloud EPG Microgateway resource, which can be put inside our Kubernetes cluster. Integration with Apigee can have more efficiency in terms of latency. Apigee is an enterprise architecture application wherein you can use a proxy.

I have been using this solution for about three years.

Amazon API Gateway is a good solution that works well most of the time. With Amazon API Gateway, I've not encountered unavailability or any issue that became a disaster.

You don't need to worry about the scalability of Amazon API Gateway because AWS takes responsibility for the solution's scalability.

I opened some tickets for use cases integrating with Lambda, and the technical support was very good. Most companies I work with use an enterprise plan from AWS. You open a chat, have your response, know what to do or what is wrong, and can resolve the problem. Amazon API Gateway's technical support is very efficient.

Positive

I have experience with Apigee.

Amazon API Gateway is very easy to set up. You can create a platform template using ChatGPT or write one with your hands.

My first Amazon API Gateway deployment took five to ten minutes. My boss requested me to expose the Lambda for internal use cases. I didn't have any experience with Amazon API Gateway at that moment, but I was able to expose the API, which was very, very easy.

In my previous company, they had a lot of people responsible for the solution's maintenance. Developers are responsible for personalizing the configurations inside Amazon API Gateway. They need to understand the requirements of the API and maximize site API. At that moment, I was responsible for having the permissions and putting the information in Amazon API Gateway. We need two or three people responsible for around 30 APIs and some developers.

Since it's a serverless solution, Amazon API Gateway is not so expensive. The pricing depends on the number of requests you have in your API, but it is adjustable. Amazon API Gateway is very good in terms of price because other solutions have a specific key price you need to pay monthly. However, with Amazon API Gateway, you pay for what you use.

If you use minimum requests inside Amazon API Gateway, you have to pay one to five dollars. However, if you have a lot of APIs, you have to pay $ 200 to $ 500. The pricing depends on how many requests you have.

If you use AWS services, do not hesitate to go for Amazon API Gateway. If you are not using AWS or if you are not AWS cloud-native, you can consider using other solutions like Apigee or Kong. If you are looking to have a serverless application, then you need to use it again.

Overall, I rate Amazon API Gateway an eight out of ten.