Head - Engineering ,Technology and Enterprise Architecture at a tech consulting company with 201-500 employees
Reseller
Top 20
Nov 24, 2025
You can proceed with your questions about Amazon API Gateway, and I will try to answer if I have the knowledge. Regarding pricing, I think it is reasonable considering the kind of work it does for us. Overall, I would rate Amazon API Gateway as a product a nine because I appreciate that product. My overall review rating for this product is nine out of ten.
I have experience with Nintex and K2, but I do not have experience with Unqork. I am specialized in Microsoft products such as Power Automate and Power Apps. I have knowledge of Microsoft Intune and Defender, along with certain Azure components. I work for an organization as a presales architect, proposing solutions to customers. I am familiar with Microsoft Defender for Identity, for Business, and for IoT, though I haven't worked extensively on that. I have a conceptually good understanding of it. I'm mostly working on Microsoft collaboration tools, which include SharePoint and Power Platform tools. I have been dealing mostly with Microsoft, but also with other vendors. Regarding database services, we typically use SQL server services. We have not used Amazon RDS; typically, we use PostgreSQL or MySQL. On the Azure side, I work with Azure Database services including PostgreSQL, MySQL, and SQL Cosmos. I was previously working as an architect for U3Soft and am currently working with Birlasoft (B I R L A S O F T). My overall rating for Amazon API Gateway is 8 out of 10.
VP at a financial services firm with 201-500 employees
Real User
Top 10
Feb 25, 2025
I would recommend Amazon API Gateway to others, but it depends on their specific needs. The overall rating is eight out of ten mainly because of the high cost.
Whenever developing APIs, be mindful of the limits, such as hard limits on the number of APIs you can develop within a region. Communicating with AWS support can provide solutions, but understanding architectural constraints is crucial. I'd rate the solution seven out of ten.
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.
Senior Professional I-Software Engineer Lead at Capgemini
Real User
Top 5
Mar 27, 2024
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.
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.
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.
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.
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.
Head of Data & ML Engineering at a financial services firm with 10,001+ employees
Real User
Sep 1, 2023
Overall, I would rate the solution a nine out of ten. There's room for enhancements. Currently, API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better.
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.
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.
Independent Technology Consultant - Financial Softwares at a tech services company with 51-200 employees
Real User
Oct 7, 2022
My company has around three to four team members who use Amazon API Gateway, but the solution is also being used by many clients who connect to it and consume APIs. Amazon API Gateway is being used daily. I advise anyone looking into using Amazon API Gateway to go ahead and use the solution. Still, you should consider your load requirements and what you're looking for in a solution before making that decision. My rating for Amazon API Gateway is nine out of ten. I'm a customer of Amazon API Gateway.
I would rate this solution 8 out of 10. If you get used to a certain technology, you would definitely recommend it to your customer because you have experience. We recommend this technology to our customers because we are using it for other products and we have experience, and then the core learning or integration course is shorter.
Cloud Engineer at a retailer with 10,001+ employees
Real User
Sep 30, 2021
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.
Software Development Manager at a financial services firm with 10,001+ employees
Real User
Sep 29, 2021
It is doing what we need at this point, there isn't anything extra that we would want. I would recommend this solution to others who are interested in using it. I would rate Amazon API Gateway a seven out of ten.
Technical Manager at a computer software company with 10,001+ employees
Real User
Dec 10, 2020
This is a good solution for anyone whose strategy is to run entirely on Amazon. You basically have to use another approach if that's not the case. If you have a hybrid cloud or if you are trying to be independent of the cloud, this is not a good solution for you. I would rate Amazon API Gateway an eight out of ten. It is a complete solution.
Sr. Technology Specialist at a computer software company with 5,001-10,000 employees
Real User
Dec 7, 2020
I recommend it for open banking. I would rate it 8 out of 10. To get to 10 it would It would need more support for open banking, via the open API. If your existing workloads are in AWS, then you can surely go for the AWS Amazon, AWS API gateway. If it is a hybrid solution, then I would suggest you go for WSA2. Konghybrid GCP is also good.
Digital Architecture Manager at a tech services company with 10,001+ employees
Real User
Jul 13, 2020
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.
I have heard complaints that people say this product does not have good security, but that is not true. There is an expectation that you can use it with other Amazon services to provide security, as well as other functionality. This is a great product. It has ease of use and a full breadth of functionality. I would say that the Amazon platform, in my view, is the best compared to third-party products. The only real problem is that you have to know a lot about what is outside of the API gateway in order to make the best use of it. I would rate this solution an eight out of ten.
Software architect at a insurance company with 10,001+ employees
Real User
Aug 11, 2019
My advice to anybody who is implementing this solution is to first read the documentation and follow the steps. Make a use case, create a proof of concept, and then migrate it to production environments. It's pretty easy to use. This is a good product, but there is always room for improvement. I would rate this solution an eight out of ten.
Director and Information Technology Architect at Fusion Professionals
Real User
Jul 16, 2019
The user interface is easy enough to use. I don't really have any complaints about it. In terms of advice for implementing and using, I would say you should make sure you've got good internal skills. I would rate this solution 8 out of 10.
Amazon API Gateway stands out for its seamless integration with AWS, ease of use, scalability, and support for secure API management, benefiting from a serverless architecture that helps control costs while ensuring efficient backend connectivity.Amazon API Gateway offers significant capabilities for managing APIs, integrating smoothly with AWS Lambda for serverless operations. It provides robust security with authentication, authorization, and input validation. The gateway supports API...
You can proceed with your questions about Amazon API Gateway, and I will try to answer if I have the knowledge. Regarding pricing, I think it is reasonable considering the kind of work it does for us. Overall, I would rate Amazon API Gateway as a product a nine because I appreciate that product. My overall review rating for this product is nine out of ten.
I have experience with Nintex and K2, but I do not have experience with Unqork. I am specialized in Microsoft products such as Power Automate and Power Apps. I have knowledge of Microsoft Intune and Defender, along with certain Azure components. I work for an organization as a presales architect, proposing solutions to customers. I am familiar with Microsoft Defender for Identity, for Business, and for IoT, though I haven't worked extensively on that. I have a conceptually good understanding of it. I'm mostly working on Microsoft collaboration tools, which include SharePoint and Power Platform tools. I have been dealing mostly with Microsoft, but also with other vendors. Regarding database services, we typically use SQL server services. We have not used Amazon RDS; typically, we use PostgreSQL or MySQL. On the Azure side, I work with Azure Database services including PostgreSQL, MySQL, and SQL Cosmos. I was previously working as an architect for U3Soft and am currently working with Birlasoft (B I R L A S O F T). My overall rating for Amazon API Gateway is 8 out of 10.
I would recommend Amazon API Gateway to others, but it depends on their specific needs. The overall rating is eight out of ten mainly because of the high cost.
I'd rate the solution ten out of ten.
Whenever developing APIs, be mindful of the limits, such as hard limits on the number of APIs you can develop within a region. Communicating with AWS support can provide solutions, but understanding architectural constraints is crucial. I'd rate the solution seven out of ten.
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.
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.
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.
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.
Overall, I would rate the solution an eight out of ten.
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.
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.
Overall, I would rate the solution a nine out of ten. There's room for enhancements. Currently, API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better.
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.
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.
I rate the solution a nine out of ten.
Overall, I would rate the solution an eight out of ten.
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.
I would rate Amazon API Gateway a nine out of ten.
My company has around three to four team members who use Amazon API Gateway, but the solution is also being used by many clients who connect to it and consume APIs. Amazon API Gateway is being used daily. I advise anyone looking into using Amazon API Gateway to go ahead and use the solution. Still, you should consider your load requirements and what you're looking for in a solution before making that decision. My rating for Amazon API Gateway is nine out of ten. I'm a customer of Amazon API Gateway.
My advice to others would be for them to keep their eye on the cost. I rate Amazon API Gateway a nine out of ten.
The suitability of this solution depends on an organization's use case and architecture. I would rate this solution an eight out of ten.
I would rate this solution 8 out of 10. If you get used to a certain technology, you would definitely recommend it to your customer because you have experience. We recommend this technology to our customers because we are using it for other products and we have experience, and then the core learning or integration course is shorter.
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.
It is doing what we need at this point, there isn't anything extra that we would want. I would recommend this solution to others who are interested in using it. I would rate Amazon API Gateway a seven out of ten.
This is a good solution for anyone whose strategy is to run entirely on Amazon. You basically have to use another approach if that's not the case. If you have a hybrid cloud or if you are trying to be independent of the cloud, this is not a good solution for you. I would rate Amazon API Gateway an eight out of ten. It is a complete solution.
I recommend it for open banking. I would rate it 8 out of 10. To get to 10 it would It would need more support for open banking, via the open API. If your existing workloads are in AWS, then you can surely go for the AWS Amazon, AWS API gateway. If it is a hybrid solution, then I would suggest you go for WSA2. Konghybrid GCP is also good.
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.
I have heard complaints that people say this product does not have good security, but that is not true. There is an expectation that you can use it with other Amazon services to provide security, as well as other functionality. This is a great product. It has ease of use and a full breadth of functionality. I would say that the Amazon platform, in my view, is the best compared to third-party products. The only real problem is that you have to know a lot about what is outside of the API gateway in order to make the best use of it. I would rate this solution an eight out of ten.
My advice to anybody who is implementing this solution is to first read the documentation and follow the steps. Make a use case, create a proof of concept, and then migrate it to production environments. It's pretty easy to use. This is a good product, but there is always room for improvement. I would rate this solution an eight out of ten.
The user interface is easy enough to use. I don't really have any complaints about it. In terms of advice for implementing and using, I would say you should make sure you've got good internal skills. I would rate this solution 8 out of 10.
I would rate this solution a five out of 10. If there was a better configuration, I'd give it a higher score.