From ff04f42beb2d728b5adde370c0b9d71f924f6504 Mon Sep 17 00:00:00 2001 From: Chris Roe Date: Sat, 25 Mar 2017 12:32:08 -0600 Subject: [PATCH] Added new tip for APIG that I got from AWS support (#394) --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 27baa22..1030ced 100644 --- a/README.md +++ b/README.md @@ -1291,7 +1291,8 @@ 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. +- 🔸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. +- 🔸API Gateway returns a 504 status code for any network or low level transport related issue. When this happens, you may see something in the cloudwatch logs for the request that says something like this: `Execution failed due to an internal error`. In reality, this means that even if your backend server is up and running, it may be doing something outside the HTTP specifications (like not sending well-formed chunked messages). Hit your backend directly with the `curl --raw -S -i ` and see if it complains. 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)