From 51e79a788132d94838cccd398282a71a71b49cb2 Mon Sep 17 00:00:00 2001 From: Surya Jakhotia Date: Fri, 19 Oct 2018 19:16:56 -0700 Subject: [PATCH] Adding API Gateway resource limitation (#642) We were bitten by this - https://medium.com/@suryaj/how-jazz-solves-aws-api-gateway-resources-limit-f023b2d04e29 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c32f9c0..2a43226 100644 --- a/README.md +++ b/README.md @@ -1589,7 +1589,7 @@ API Gateway - In particular, when deploying an API Gateway as part of a CloudFormation stack, changes will not automatically deploy unless the deployment resource itself was changed. You can change work around this by always changing the deployment resource on a CloudFormation update, or running a custom resource that ensures the deployment is made. - Alternatively, by using the [Serverless Application Model](https://github.com/awslabs/serverless-application-model) definition for an API Gateway resource, you can always expect the API to be deployed on a stack update since SAM will generate a new deployment every time. - 🔸API Gateway does not support nested query parameters on method requests. - +- 🔸API Gateway limits number of resources to 300, as described [here](http://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#api-gateway-limits). This is something to be considered when you start using API Gateway as a platform where your team/organization deploys to the same API Gateway. 🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)