1
0
Fork 0
mirror of https://github.com/nickpoida/og-aws.git synced 2025-02-13 10:21:57 +00:00

Merge pull request #273 from muhqu/patch-2

API Gateway gotcha Multi-Region
This commit is contained in:
Joshua Levy 2016-10-29 00:37:20 -07:00 committed by GitHub
commit f4eec650a4

View file

@ -1174,6 +1174,7 @@ API Gateway
- 🔸API Gateway only supports encrypted (https) endpoints, and does not support unencrypted HTTP. (This is probably a good thing.) - 🔸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 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 Amazons edge locations (like a CloudFront Distribution). You can not have multiple API Gateways with the same hostname in different AWS Regions and use Route 53 to distribute the traffic. See this [AWS forum post](https://forums.aws.amazon.com/thread.jspa?messageID=735342&#735342) for more information.
🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md) 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)