AWS AmazonCloudWatch documentation change
Summary
Added documentation for CloudWatch Observability Admin service quotas and API rate limits
Security assessment
The changes introduce quota limits for a new Observability Admin service focused on managing telemetry configurations. While auditing/monitoring configurations can relate to security posture, there is no explicit mention of security vulnerabilities, access controls, or protective features. The documentation describes operational limits rather than security capabilities.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.md b/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.md index ca920edaf..ac6954b8c 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch_limits.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch_limits.md @@ -5 +5 @@ -CloudWatchCloudWatch investigations (Amazon AI Operations)CloudWatch Application InsightsCloudWatch Application SignalsInternet MonitorNetwork Flow MonitorNetwork Synthetic MonitorCloudWatch Observability Access ManagerCloudWatch RUM Managing your CloudWatch service quotas +CloudWatchCloudWatch investigations (Amazon AI Operations)CloudWatch Application InsightsCloudWatch Application SignalsInternet MonitorNetwork Flow MonitorNetwork Synthetic MonitorCloudWatch Observability Access ManagerCloudWatch Observability AdminCloudWatch RUM Managing your CloudWatch service quotas @@ -32,0 +33,2 @@ For some AWS services including CloudWatch, you can use the CloudWatch usage met + * CloudWatch Observability Admin + @@ -207,0 +210,32 @@ Rate of UpdateLink requests | Each supported Region: 10 per second | No | Maximu +## CloudWatch Observability Admin + +CloudWatch Observability Admin helps you discover, audit, and manage CloudWatch telemetry configurations across an AWS account or organization. It provides a consolidated view of monitoring settings for resources, enabling you to ensure consistent and proper data collection by simplifying the management of telemetry across multiple accounts. Most quotas are adjustable to accommodate enterprise-scale deployments that need higher limits for managing observability rules across large organizations. + +Name | Default | Adjustable | Description +---|---|---|--- +CreateCentralizationRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of create-centralization-rule-for-organization calls per second per account/per region +CreateTelemetryRule throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of create-telemetry-rule calls per second per account/per region +CreateTelemetryRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of create-telemetry-rule-for-organization calls per second per account/per region +DeleteCentralizationRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of delete-centralization-rule-for-organization calls per second per account/per region +DeleteTelemetryRule throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of delete-telemetry-rule calls per second per account/per region +DeleteTelemetryRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of delete-telemetry-rule-for-organization calls per second per account/per region +GetCentralizationRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of get-centralization-rule-for-organization calls per second per account/per region +GetTelemetryEnrichmentStatus throttle limit in transactions per second | Each supported Region: 5 per second | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-B19247CC) | The maximum number of GetTelemetryEnrichmentStatus calls per second per account and per region +GetTelemetryRule throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of get-telemetry-rule calls per second per account/per region +GetTelemetryRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of get-telemetry-rule-for-organization calls per second per account/per region +ListCentralizationRulesForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of list-centralization-rules-for-organization calls per second per account/per region +ListTagsForResource throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of list-tags-for-resource calls per second per account/per region +ListTelemetryRules throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of list-telemetry-rules calls per second per account/per region +ListTelemetryRulesForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of list-telemetry-rules-for-organization calls per second per account/per region +Logs Centralization throughput per destination region | Each supported Region: 250 Megabytes per second | No | The maximum organization-level throughput for centralization of logs per destination region +Organization Centralization Rules | Each supported Region: 50 | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-B8EC8109) | The maximum number of organization centralization rules that you can create for an organization +Organization Telemetry Rules | Each supported Region: 50 | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-74ABF7EB) | The maximum number of organization telemetry rules that you can create for an organization +StartTelemetryEnrichment throttle limit in transactions per second | Each supported Region: 1 per second | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-E3DAB469) | The maximum number of StartTelemetryEnrichment calls per second per account and per region +StopTelemetryEnrichment throttle limit in transactions per second | Each supported Region: 1 per second | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-C6A78D4B) | The maximum number of StopTelemetryEnrichment calls per second per account and per region +TagResource throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of tag-resource calls per second per account/per region +Telemetry Rules | Each supported Region: 5 | [Yes](https://console.aws.amazon.com/servicequotas/home/services/observabilityadmin/quotas/L-A344069D) | The maximum number of telemetry rules that you can create for an account +UntagResource throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of untag-resource calls per second per account/per region +UpdateCentralizationRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of update-centralization-rule-for-organization calls per second per account/per region +UpdateTelemetryRule throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of update-telemetry-rule calls per second per account/per region +UpdateTelemetryRuleForOrganization throttle limit in transactions per second | Each supported Region: 5 | No | The maximum number of update-telemetry-rule-for-organization calls per second per account/per region +