Amazon API Gateway Reviews & Insights

I would say we are satisfied with the services provided by Amazon API Gateway to our project and to our company. We were trying API Gateway on lambdas and it helped our project to get to the milestone where we would tried to reach. We communicated lambdas to complete the micro services flow.

Amazon API Gateway is enhanced platform for developers team to build, Quality testing, arrange and deploy API both restful and websocket based. It provides excellant integration with other services in all kind of enviorments and helps all the different teams in project lofe cycle ranging between dev, QA and UAT.

In our organization, Amazon API Gateway helps developers to manage, create, publish, maintain, monitor, and secure APIs of any and all scales. It helps a lot in streamlining administrations. It has a fantastic setup and security for hosting REST APIs that comply with HIPPA guidelines and regulations. Its operation is very easy to use and flexible.

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

We use Amazon API Gateway at the IT department for all internal and external tools integration which involves web services. Our organization uses Amazon API Gateway to have an authentication layer and security for all the public-facing web services. It helped our organization to have better security and zero downtime for new version deployments.

Amazon API Gateway is powerful service where any organization/team can start developing webs services in less than few hours. It is well suited integration with any other AWS services like Lamda, Cloudwatch etc.. Easy to add authentication layer for web services and deployment with multiple versions. As it is server less, billing is based on usage.

We are using API Gateway (API GW) as an HTTP front end for internal resources including lambda functions and load-balanced web applications. Other teams are using API GW as integration for static resources.

The main problem that API GW addresses for us is providing an authorization management point for access to internal services. We can use the API keys, authorization hooks, and usage plans to really dial in who can access our applications while controlling how they access them.

API GW is great for giving access to asynchronous operations that are fast and don't need to be online all the time. Lambda functions are the classic example.

In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond.

If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.

We use the [Amazon] API Gateway across the enterprise. Today it is our main communication channel, when it comes to APIs, because it is quite robust, and at the same time flexible enough to be managed and used in the daily activities of different teams, with the necessary security controls. It solved a problem of centralization, simplified management and access control of the APIs.

We needed a tool that aggregates the APIs, allowing central control, and at the same time reducing the delivery time of the solutions, without worrying about scalability or security. This solution solved these points in a very simple way, giving us even more security (simple things like putting a certificate in front, it delivers for free), and connecting to the services we already used within AWS.

Our organization uses Amazon API Gateway to orchestrate and consolidate web service APIs across projects. It is a useful multi-purpose tool, and we use it to integrate authentication to our APIs, build out consolidated responses from different API endpoints, and to provide a single point of access to multiple web service APIs developed using a myriad of different technologies and programming languages. It also provides a great way to document and integrate web services via Swagger integrations.

If you are using AWS as your primary infrastructure provider, [Amazon] API Gateway is the best gateway option for you to integrate and expose web service applications. It integrates well with security controls provided by AWS such as VPC limits and security groups. Furthermore, it is very easy to use Amazon API Gateway to provide an out-of-the-box auth solution by integrating AWS Cognito. We were able to get authentication and authorization integrated very quickly in to a large number of APIs under the same product umbrella by utilizing API Gateway's integration with Cognito.
[Amazon] API Gateway is not the best solution if you're trying to build a microservices architecture, as it's service registration methodology is still quite clunky. For microservices, you'd be better off utilizing tools built specifically for that purpose.

Amazon API Gateway is used to migrate existing legacy apps and to create new apps based on the latest department initiatives. It is allowing us to generate more "generic" APIs that can be easily shared across different applications and it is easier to develop with lambda behind it. We are now moving more and more towards cloud and serverless and this perfectly fit our needs.

It is great if you want to have a single point of entry that is scalable and has redundancy but be prepared to spend days not being able to figure out what the problem is and how to solve it. Errors are not very descriptive, it lacks documentation to explain the basic flow of data in this service, and troubleshooting issues especially CORS is a nightmare. Until we hired AWS Developer to have a 2-day session to go through this service and how to set it up and use it, it was just a nightmare. And even after having a session they still did not explain all the features and setup, they pointed us to documentation, but documentation is not very well written.

Our team develops several APIs for multiple end-users to consume. These are both internal and external customers. Our services are behind the Amazon API Gateway. This helps in securing our APIs and also helps curtail misuse of our APIs by bad actors. Thus Amazon API Gateway is helping us a great deal as we put a lot of the administration efforts within the gateway itself instead of our code.

Amazon API Gateway is one of the best way to host your services under the AWS umbrella and easy to provide scalability and reliability. Our company is exposing an API service to various clients with custom billing and limitation. In this task, Amazon API provides a great infrastructure and security to host REST APIs with HIPAA compliances.

Amazon API Gateway is a very powerful tool, for a small organization. Good for quick developing microservices . It is also great when used as a API gateway that provides authentication over microservices.

Amazon API Gateway has been adopted by multiple teams within our organization.
It offers an intuitive easy-to-use entry point to the AWS serverless services, and has helped our team move traditional 3-tier web applications to the cloud with ease.

It is best suited for building out the APIs for a serverless backend. It may not be the best option for Mobile backends, in which case AWS AppSync would be preferred over API Gateway.