From eecf85b73f2a4fe778692ea81d95f9f2b97dcbe6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A5rten=20Gustafson?= Date: Fri, 14 Oct 2016 10:54:27 +0200 Subject: [PATCH] Remove redundant point about API Gateway endpoints --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 196cfa3..c648a4a 100644 --- a/README.md +++ b/README.md @@ -1068,7 +1068,6 @@ API Gateway ### API Gateway Gotchas and Limitations - 🔸API Gateway only supports encrypted (https) endpoints, and does not support unencrypted HTTP. (This is probably a good thing.) -- 🔸API Gateway endpoints are public — there is no mechanism to build private endpoints, e.g. for internal use. - 🔸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). 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)