From b1b75f5170315af5021624840060e2cee68cdacd Mon Sep 17 00:00:00 2001 From: Artem Nikitin Date: Tue, 17 Jan 2017 05:38:40 +0100 Subject: [PATCH] Add info about limitations for API Gateway (#372) * Add info about limitations for API Gateway * Fix description --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 31e92aa..fcba8fa 100644 --- a/README.md +++ b/README.md @@ -1285,6 +1285,7 @@ API Gateway - 🔸API Gateway only supports encrypted (https) endpoints, and does not support unencrypted HTTP. (This is probably a good thing.) - 🔸API Gateway endpoints are always public, i.e. internet facing, and there is no mechanism to build private endpoints, e.g. for internal use on a [VPC](#vpcs-network-security-and-security-groups) but endpoints and their related resources can, optionally, [require authentication](http://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html). - 🔸API Gateway doesn’t support multi-region deployments for high availability. It is a service that is deployed in a single region but comes with a global endpoint that is served from AWS edge locations (similar to a CloudFront distribution). You cannot have multiple API Gateways with the same hostname in different AWS regions and use Route 53 to distribute the traffic. More in [this forum post](https://forums.aws.amazon.com/thread.jspa?messageID=735342򳡮). +- 🔸Integration timeout: All of the various integration types (eg: Lambda, HTTP) for API Gateway have timeouts, as described [here](http://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#api-gateway-limits). Unlike some limits, these timeouts can't be increased. 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)