AWS cost-management documentation change
Summary
Expanded quota details for anomaly detection monitors, added billing view limits, and clarified detection time/data requirements.
Security assessment
Changes focus on operational quotas and monitoring capabilities. While detection delays (24 hours) could indirectly impact security response, the documentation does not address a specific security vulnerability or introduce security controls.
Diff
diff --git a/cost-management/latest/userguide/management-limits.md b/cost-management/latest/userguide/management-limits.md index 2967abf77..2b01b034b 100644 --- a//cost-management/latest/userguide/management-limits.md +++ b//cost-management/latest/userguide/management-limits.md @@ -38,0 +39 @@ Total number of budgets per management account | 20,000 +Total number of budgets using a custom billing view | 150 @@ -63 +64,19 @@ Maximum number of filters in the `GetCostAndUsage` operation (API) | 100 -Maximum number of anomaly monitors you can create for an AWS services monitor type | 1 monitor per account +**AWS Managed Monitor Quotas** + +AWS managed monitor for AWS services per account (management and member) | 1 +---|--- +Additional AWS managed monitors (linked account, cost allocation tag, or cost category) per management account | 1 +Total AWS managed monitors per management account | 2 +Total AWS managed monitors per member account | 1 +Values tracked per AWS managed monitor | 5,000 + +**Customer Managed Monitor Quotas** + +Total customer managed monitors per management account | 500 +---|--- +Values per customer managed monitor (linked accounts or tag values) | 10 +Values per customer managed monitor (cost category values) | 1 + +**General Quotas (Apply to Both)** + +Alert subscriptions per account | 100 @@ -65,2 +84,5 @@ Maximum number of anomaly monitors you can create for an AWS services monitor ty -Maximum number of anomaly monitors you can create for other monitor types (linked account, cost category, cost allocation tag) | 500 total monitors per management account -Maximum number of anomaly alert subscriptions you can create | 100 subscriptions per account +Email recipients per subscription | 10 +Amazon SNS topics per subscription | 1 +Monitors per alert subscription | 502 maximum (all monitors can be attached) +Time to detect anomaly after usage | Up to 24 hours +Historical data required for detection | 10 days minimum @@ -77 +99 @@ Unsupported services | - * Upfront and recurring reserved fee and Savings Plan fees + * Only analyzes Usage charge type and NetUnblendedCost