API Gateway helped us solve a problem we were encroaching, which was too many endpoints with not enough organization. APIGW let us take our endpoints and isolate them. The routing lets us write specific endpoints which then become simple to deploy, upkeep and monitor. Additionally, the security features available keep our API secure from misuse.

We liked how easy it was to connect to cloud functions. Previously, our APIs were written and hosted on an EC2 server. It was extremely easy to create a function on Lambda that was accessible to the outside through API Gateway. Also, the authorizations and authentication using Apikeys / custom authorizers allowed us to have multiple levels of users and security, which some of our older endpoints did not have.

We have a recurring problem with the timeout limit on the API. There are some APIs we want to develop but are unable to due to the timeout limit (30s) Some features I don't think are helpful. For example, the API documentation section I think is lacking and using a different Documentation system is preferred. Also, we wanted to view the usage per api key but to do so required a custom logging solution with Amazon Firehose. I would imagine such functionality should be available through the dashboard or Cloudwatch.

It fulfilled our needs for centralized and securing all our microservices deployed in the AWS infrastructure. The service price is included and only charges a price on your destination app.

All of our services were deployed in the AWS infrastructure and to enable communication between them, we used the secured API Gateway service. It lets us customize every method and microservice endpoint in a non-technical interface. The gateway also allowed us to centralize all the calls making the documentation more accessible.

There wasn't any issue regarding this implementation, everything about the API Gateway is very well documented, and the interface is full of tooltips.

For business running their workloads completely in AWS, AWS API Gateway is a great fit to be positioned as a n entry point.

- Seamlessly integrated with quite a few AWS services helping customers to roll out solutions quickly - Extremely easy to onboard a passthrough proxy API - Offers support for a wide range of security options

- When it comes to addressing transformation requirements, AWS API Gateway makes use of Velocity Template language which is less known and popular in comparison to other popular languages. So there is a learning curve

Like so many AWS products, you never use an API Gateway in isolation. The majority of your work will be with the AWS Lambda and data source. Once you define your Gateway, it's easy to build a stub service for testing and incrementally work on it until you are done.

API Gateway makes writing REST APIs easy. Combine it with an AWS Lambda and a data source and you're basically done. The end result is easy to test with a tool like Postman.

I personally dislike the AWS Console interface for AWS Gateways. There's nothing really wrong with it as it is functional, but it could be better integrated by providing a more direct connection to the underlying services and it could provide better "testing data" in the default options to test from the console.

We have used API gateway to maintain all our backend APIs and it has reduced tons of work since a lot of features such authentication, rate-limiting , logging , staging is included in the service.

1. Serverless approach to manage APIs2. Rate limiting3. Advanced logging and monitoring, can be connected to cloudwatch4. Integrates perfectly with Lambdas and other compute AWS services

Includes a hard limit of 29 seconds which does not work well if you have long-running code.