AWS cost-management documentation change
Summary
Added guidance about using customer-managed monitors and SNS topics for granular alert thresholds when using AWS managed anomaly detection
Security assessment
The change provides operational guidance for alert configuration but does not introduce security features or address security vulnerabilities.
Diff
diff --git a/cost-management/latest/userguide/edit-alert-pref.md b/cost-management/latest/userguide/edit-alert-pref.md index b734d42eb..1069c2eb0 100644 --- a//cost-management/latest/userguide/edit-alert-pref.md +++ b//cost-management/latest/userguide/edit-alert-pref.md @@ -10,0 +11,13 @@ You can also edit your notification configurations in AWS User Notifications. +###### Note + +When using AWS managed monitors, consider that a single threshold applies to all tracked values. If you need different alert thresholds for different teams or accounts, you can: + + * Create supplementary customer managed monitors with dedicated alert subscriptions with specific thresholds + + * Use AWS User Notifications to filter and route alerts based on anomaly attributes + + * Configure Amazon Amazon SNS topics with custom logic for alert routing + + + + @@ -78 +91 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Getting started with AWS Cost Anomaly Detection +Transitioning from customer to AWS managed monitors