AWS cognito documentation change
Summary
Clarified MAU counting for federated users and added pricing link
Security assessment
Billing documentation update with no direct security implications
Diff
diff --git a/cognito/latest/developerguide/quotas.md b/cognito/latest/developerguide/quotas.md index a64324d9a..18b856b32 100644 --- a//cognito/latest/developerguide/quotas.md +++ b//cognito/latest/developerguide/quotas.md @@ -52 +52 @@ For example, if your quota for the `UserAuthentication` category is 80 RPS, you -When Amazon Cognito calculates user pool billing, it charges you a rate for each _monthly active user (MAU)_. Consider your current and projected MAU count in your planning for quota increase requests. A user is counted as a MAU if, within a calendar month, there is an identity operation related to that user. When you [link federated users to local users](./cognito-user-pools-identity-federation-consolidate-users.html), the MAU count is one plus _n_ , where _n_ is the number of linked identities that have signed in. The activities that make a user active include the following. +When Amazon Cognito calculates user pool billing, it charges you a rate for each _monthly active user (MAU)_. Consider your current and projected MAU count in your planning for quota increase requests. A user is counted as a MAU if, within a calendar month, there is an identity operation related to that user. When you [link federated users to local users](./cognito-user-pools-identity-federation-consolidate-users.html), with SAML or OIDC federation, the local user will count as an enterprise directory MAU or `EnterpriseMAU`, regardless of whether the user signs in directly or via federation. See [Amazon Cognito Pricing](https://aws.amazon.com/cognito/pricing/) for more information.