AWS IDR documentation change
Summary
Restructured documentation with improved section headings ('About workloads' and 'About alarms'), removed redundant content, updated links to onboarding/alarm ingestion guides, and eliminated an image reference.
Security assessment
The changes are editorial improvements focused on clarity and structure. No security vulnerabilities, weaknesses, or incidents are referenced. While the content discusses incident response (a security-adjacent area), it doesn't introduce new security features or address specific security flaws. The alarm configuration guidance emphasizes operational best practices rather than security controls.
Diff
diff --git a/IDR/latest/userguide/getting-started-idr.md b/IDR/latest/userguide/getting-started-idr.md index 8a9dc4862..1e351048c 100644 --- a//IDR/latest/userguide/getting-started-idr.md +++ b//IDR/latest/userguide/getting-started-idr.md @@ -7 +7 @@ -WorkloadsAlarms +About workloadsAbout alarms @@ -9 +9 @@ WorkloadsAlarms -# Get started in Incident Detection and Response +# Get started with Incident Detection and Response @@ -11 +11 @@ WorkloadsAlarms -Workloads and alarms are central to AWS Incident Detection and Response. AWS works closely with you to define and monitor specific workloads that are critical to your business. AWS helps you set up alarms that quickly notify your team of significant performance issues or customer impact. Properly configured alarms are essential for proactive monitoring and rapid incident response within Incident Detection and Response. +Workloads and alarms are central to AWS Incident Detection and Response. AWS works closely with you to define and monitor specific workloads that are critical to your business. AWS helps you set up alarms that notify your team of significant performance issues or customer impact. Properly configured alarms are essential for proactive monitoring and rapid incident response within Incident Detection and Response. @@ -13 +13 @@ Workloads and alarms are central to AWS Incident Detection and Response. AWS wor -## Workloads +## About workloads in Incident Detection and Response @@ -17 +17 @@ You can select specific workloads for monitoring and critical incident managemen -For example, you might have a monolithic application hosted in a single account (for example, Employee Performance App in the following diagram). Or, you might have an application (for example, Storefront Webapp in the diagram) broken into microservices that stretch across different accounts. A workload might share resources, such as a database, with other applications or workloads, as shown in the diagram. +For example, you might have a monolithic application hosted in a single account (for example, Employee Performance App in the following diagram). Or, you might have an application (for example, Storefront Webapp in the diagram) broken into microservices that stretch across different accounts. A workload might share resources, such as a database, with other applications or workloads, as shown in the following diagram. @@ -19 +19 @@ For example, you might have a monolithic application hosted in a single account - +To get started with workload onboarding, see [Onboard workloads to Incident Detection and Response](./idr-gs-onboard-workload.html). @@ -21 +21 @@ For example, you might have a monolithic application hosted in a single account -To get started with workload onboarding, see [Workload onboarding](./idr-gs-onboard-workload.html#workload-onboarding) and [Workload onboarding questionnaire](./idr-gs-questionnaire.html). +## About alarms in Incident Detection and Response @@ -23 +23 @@ To get started with workload onboarding, see [Workload onboarding](./idr-gs-onbo -## Alarms +Alarms are a key part of Incident Detection and Response. Alarms provide visibility into the performance of your applications and underlying AWS infrastructure. AWS works with you to define appropriate metrics and alarm thresholds that only trigger when there is critical impact to your monitored workloads. The goal is for alarms to engage your specified resolvers, who then collaborate with the incident management team to quickly mitigate issues. Configure your alarms to only enter the **Alarm** state when there is a significant degradation in performance or customer experience that requires immediate attention. Some key types of alarms include those that indicate business impact, Amazon CloudWatch canaries, and aggregate alarms that monitor dependencies. @@ -25,7 +25 @@ To get started with workload onboarding, see [Workload onboarding](./idr-gs-onbo -Alarms are a key part of Incident Detection and Response, as they provide visibility into the performance of your applications and underlying AWS infrastructure. AWS works with you to define appropriate metrics and alarm thresholds that will only trigger when there is critical impact to your monitored workloads. The goal is for alarms to engage your specified resolvers, who can then collaborate with the incident management team to quickly mitigate any issues. Alarms should be configured to only enter the Alarm state when there is a significant degradation in performance or customer experience that requires immediate attention. Some key types of alarms include those that indicate business impact, Amazon CloudWatch canaries, and aggregate alarms that monitor dependencies. - -To get started with alarm ingestion, see [Alarm ingestion](./idr-gs-onboard-workload.html#alarm-ingestion) and [Alarm ingestion questionnaire](./idr-gs-questionnaire.html). - -###### Note - -To make changes to your runbooks, workload information, or the alarms monitored on AWS Incident Detection and Response, see [Request changes to an onboarded workload in Incident Detection and Response](./idr-workloads-change-request.html). +To get started with alarm ingestion, see [Alarm Ingestion](./idr-gs-alarm-ingestion.html). @@ -41 +35 @@ Region availability -Onboarding +Onboard workloads