AWS cost-management documentation change
Summary
Updated descriptions of daily/weekly summary alerts to clarify notification requirements and content structure
Security assessment
Changes focus on clarifying notification mechanics and requirements without introducing security concepts or addressing vulnerabilities
Diff
diff --git a/cost-management/latest/userguide/getting-started-ad.md b/cost-management/latest/userguide/getting-started-ad.md index ebe2f4137..e2e75756f 100644 --- a/cost-management/latest/userguide/getting-started-ad.md +++ b/cost-management/latest/userguide/getting-started-ad.md @@ -74 +74 @@ You can configure the Amazon SNS topic to create an Amazon Q Developer in chat a - * **Daily summaries** \- An email notification with a daily summary of top 10 alerts from the previous day, sorted by cost impact. The system generates this summary at 00:00 UTC daily, though actual delivery time may vary. For example, an anomaly detected at 04:30 UTC on January 14 will be included in the daily summary sent at 00:00 UTC on January 15. At least one email recipient must be specified. For immediate alerts, we recommend using the individual alerts option. + * **Daily summaries** \- The alert notifies you with a daily summary when anomalies are detected. You receive one email that contains information for multiple anomalies that occurred that day. These notifications require at least one email recipient. @@ -76 +76 @@ You can configure the Amazon SNS topic to create an Amazon Q Developer in chat a - * **Weekly summaries** \- An email notification with a weekly summary of alerts. You receive one email per week containing information about multiple anomalies that occurred during that week. At least one email recipient must be specified. + * **Weekly summaries** \- The alert notifies you with a weekly summary when anomalies are detected. You receive one email that contains information for multiple anomalies that occurred that week. These notifications require at least one email recipient. @@ -119 +119 @@ You must create at least one alert subscription for each monitor. The "create co -You can configure the Amazon SNS topic to create an Amazon Q Developer in chat applications configuration that maps the SNS topic to a Slack channel or an Amazon Chime chat room. For more information, see [Receiving anomaly alerts in Amazon Chime and Slack](./cad-alert-chime.html). +You can configure the Amazon SNS topic to create an Amazon Q Developer in chat applications configuration. This configuration maps the SNS topic to a Slack channel or an Amazon Chime chat room. For more information, see [Receiving anomaly alerts in Amazon Chime and Slack](./cad-alert-chime.html). @@ -121 +121 @@ You can configure the Amazon SNS topic to create an Amazon Q Developer in chat a - * **Daily summaries** \- An email notification with a daily summary of top 10 alerts from the previous day, sorted by cost impact. The system generates this summary at 00:00 UTC daily, though actual delivery time may vary. For example, an anomaly detected at 04:30 UTC on January 14 will be included in the daily summary sent at 00:00 UTC on January 15. At least one email recipient must be specified. For immediate alerts, we recommend using the individual alerts option. + * **Daily summaries** \- The alert notifies you with a daily summary when anomalies are detected. You receive one email that contains information for multiple anomalies that occurred that day. These notifications require at least one email recipient. @@ -123 +123 @@ You can configure the Amazon SNS topic to create an Amazon Q Developer in chat a - * **Weekly summaries** \- An email notification with a weekly summary of alerts. You receive one email per week containing information about multiple anomalies that occurred during that week. At least one email recipient must be specified. + * **Weekly summaries** \- The alert notifies you with a weekly summary when anomalies are detected. You receive one email that contains information for multiple anomalies that occurred that week. These notifications require at least one email recipient.