AWS AmazonCloudWatch documentation change
Summary
Added incident report notification integration with chat channels and updated documentation links. Enhanced guidance on sending investigation reports to collaboration tools.
Security assessment
Introduces notification capabilities for incident reports, which improves incident response visibility but doesn't address a specific security flaw. The change documents security-adjacent operational practices rather than resolving vulnerabilities.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md b/AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md index 981c48236..547b799e4 100644 --- a//AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md +++ b//AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md @@ -32 +32 @@ Automation provides over 400 AWS managed runbooks. For details about each runboo -For information about working with runbooks in an investigation, see [Reviewing and executing suggested runbook remediations for CloudWatch investigations](./Investigations-Investigate.html#suggested-investigation-actions). +For information about working with runbooks in an investigation, see [Reviewing and executing suggested runbook remediations for CloudWatch investigations](./suggested-investigation-actions.html). @@ -110,0 +111,2 @@ If you have already created an investigation group and want to add chat integrat +When incident reports are generated, notifications can be sent to configured chat channels to alert team members that new documentation is available. These notifications include links to the generated reports and can be customized to include key findings or action items. + @@ -117 +119 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Cross-account investigations +Generate a report from an investigation