From 98192b853cf0fcbb46fa036ce801d3c11e283816 Mon Sep 17 00:00:00 2001 From: AJ Kerrigan Date: Wed, 11 Jan 2017 13:19:47 -0500 Subject: [PATCH] Add information about service limits (#359) Reference the awslimitchecker tool as well as its documentation, which helps identify available ways to check various limits. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 6d6aec8..ac31368 100644 --- a/README.md +++ b/README.md @@ -399,6 +399,7 @@ It’s important to know the maturity of each AWS product. Here is a mostly comp ### Restrictions and Other Notes - 🔸Lots of resources in Amazon have [**limits**](http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) on them. This is actually helpful, so you don’t incur large costs accidentally. You have to request that quotas be increased by opening support tickets. Some limits are easy to raise, and some are not. (Some of these are noted in sections below.) + - **Obtaining Current Limits and Usage:** Limit information for a service may be available from the service API, Trusted Advisor, both or neither (in which case you'll need to contact Support). [This page](http://awslimitchecker.readthedocs.io/en/latest/limits.html) from the awslimitchecker tool's documentation provides a nice summary of available retrieval options for each limit. The [tool](https://github.com/jantman/awslimitchecker) itself is also valuable for automating limit checks. - 🔸[**AWS terms of service**](https://aws.amazon.com/service-terms/) are extensive. Much is expected boilerplate, but it does contain important notes and restrictions on each service. In particular, there are restrictions against using many AWS services in **safety-critical systems**. (Those appreciative of legal humor may wish to review clause 57.10.) ### Related Topics