AWS IDR documentation change
Summary
Updated incident management process documentation with minor text formatting changes, added details about AWS service event detection timing, and removed redundant content
Security assessment
Changes focus on clarifying incident management procedures and timing of service event detection. While improved incident response processes can have security implications, there is no direct evidence of addressing a specific security vulnerability or weakness. The changes enhance operational documentation rather than introduce security controls.
Diff
diff --git a/IDR/latest/userguide/incidents-idr.md b/IDR/latest/userguide/incidents-idr.md index 774ee9299..7e592056a 100644 --- a//IDR/latest/userguide/incidents-idr.md +++ b//IDR/latest/userguide/incidents-idr.md @@ -7 +7 @@ -AWS Incident Detection and Response offers you 24x7 proactive monitoring and incident management delivered by a designated team of incident managers. The following diagram outlines the standard incident management process when an application alarm triggers an incident, including alarm generation, AWS Incident Manager engagement, incident resolution, and post-incident review. +AWS Incident Detection and Response offers you 24 hours a day, 7 days a week proactive monitoring and incident management delivered by a designated team of incident managers. The following diagram outlines the standard incident management process when an application alarm triggers an incident, including alarm generation, AWS Incident Manager engagement, incident resolution, and post-incident review. @@ -11 +11 @@ AWS Incident Detection and Response offers you 24x7 proactive monitoring and inc - 1. **Alarm Generation** : Alarms triggered on your workloads are pushed through Amazon EventBridge to AWS Incident Detection and Response. AWS Incident Detection and Response automatically pulls up the runbook associated with your alarm and notifies an incident manager. If a critical incident occurs on your workload that isn't detected by alarms monitored by AWS Incident Detection and Response, then you can create a support case to request an Incident Response. For more information on requesting an Incident Response, see [Request an Incident Response](./inbound-incident-idr.html). + 1. **Alarm generation** : Alarms triggered on your workloads are pushed through Amazon EventBridge to AWS Incident Detection and Response. AWS Incident Detection and Response automatically pulls up the runbook associated with your alarm and notifies an incident manager. If a critical incident occurs on your workload that isn't detected by alarms monitored by AWS Incident Detection and Response, then you can create a support case to request an Incident Response. For more information on requesting an Incident Response, see [Request an Incident Response](./inbound-incident-idr.html). @@ -13 +13 @@ AWS Incident Detection and Response offers you 24x7 proactive monitoring and inc - 2. **AWS Incident Manager Engagement** : The incident manager responds to the alarm and engages you on a conference call or as otherwise specified in the runbook. The incident manager verifies the health of the AWS services to determine if the alarm is related to issues with AWS services used by the workload and advises on the status of the underlying services. If required, the incident manager then creates a case on your behalf and engages the right AWS experts for support. + 2. **AWS Incident Manager engagement** : The incident manager responds to the alarm and engages you on a conference call or as otherwise specified in the runbook. The incident manager verifies the health of the AWS services to determine if the alarm is related to issues with AWS services used by the workload and advises on the status of the underlying services. If required, the incident manager then creates a case on your behalf and engages the right AWS experts for support. Because AWS Incident Detection and Response monitors AWS services specifically for your applications, AWS Incident Detection and Response might determine that the incident is related to an AWS service issue before an AWS service event is declared. In this scenario, the incident manager advises you on the status of the AWS service, triggers the AWS service event incident management workflow, and follows up with the service team on resolution. The information provided gives you the opportunity to implement your recovery plans or workarounds early to mitigate the impact of the AWS service event. @@ -15,3 +15 @@ AWS Incident Detection and Response offers you 24x7 proactive monitoring and inc -Because AWS Incident Detection and Response monitors AWS services specifically for your applications, AWS Incident Detection and Response might determine that the incident is related to an AWS service issue even before an AWS service event is declared. In this scenario, the incident manager advises you on the status of the AWS service, triggers the AWS Service Event Incident Management flow, and follows up with the service team on resolution. The information provided gives you the opportunity to implement your recovery plans or workarounds early to mitigate the impact of the AWS Service Event. For more information, see [Incident management for service events](./idr-inc-mgmt-serv-events.html). - - 3. **Incident Resolution** : The incident manager coordinates the incident across the required AWS teams and makes sure that you remain engaged with the right AWS experts until the incident is mitigated or resolved. + 3. **Incident resolution** : The incident manager coordinates the incident across the required AWS teams and makes sure that you remain engaged with the right AWS experts until the incident is mitigated or resolved. @@ -68,2 +65,0 @@ The following report template is an example only. - * [Incident management for service events](./idr-inc-mgmt-serv-events.html) -