AWS prescriptive-guidance documentation change
Summary
Minor grammatical edits, updated image path, and typographical changes to bullet point dashes
Security assessment
Changes involve punctuation adjustments (removing commas, changing en-dashes to horizontal bars), an image path update, and grammatical rephrasing. No security vulnerabilities, security features, or security-related content was added or modified. The changes maintain focus on chaos engineering metrics and organizational practices without introducing security context.
Diff
diff --git a/prescriptive-guidance/latest/chaos-engineering-on-aws/getting-started.md b/prescriptive-guidance/latest/chaos-engineering-on-aws/getting-started.md index f46ff94b5..229e5a500 100644 --- a//prescriptive-guidance/latest/chaos-engineering-on-aws/getting-started.md +++ b//prescriptive-guidance/latest/chaos-engineering-on-aws/getting-started.md @@ -19 +19 @@ Before you conduct an experiment, we recommend that you put a few essentials in - * Prioritization of critical findings, based on potential business impact, over new features that are discovered when running chaos experiments + * Prioritization of critical findings based on potential business impact over new features that are discovered when running chaos experiments @@ -32 +32 @@ The following diagram shows the types of metrics that you can track for chaos ex - + @@ -79 +79 @@ Chaos engineering provides the most value when it's applied across your organiza -To support the business case of building a chaos engineering practice, attach chaos engineering efforts to your critical business projects. Making resilience an asset and driver for acceleration will help you track success over time. Start with a count of critical incidents per month or per quarter, the average time to recover, and the impact that these incidents caused to your customers and organization. Set a goal with your teams to reduce the number of incidents over a 6 to 12-month period as improvements are made across your application stacks in response to chaos engineering experiments. +To support the business case of building a chaos engineering practice, attach chaos engineering efforts to your critical business projects. Making resilience an asset and driver for acceleration will help you track success over time. Start with a count of critical incidents per month or per quarter, the average time to recover, and the impact that these incidents caused to your customers and organization. Set a goal with your teams to reduce the number of incidents over a 6-month to 12-month period as improvements are made across your application stacks in response to chaos engineering experiments. @@ -85 +85 @@ To track progress in chaos engineering over time, capture the following metrics - * **Reduced incident rate** – Track the number of production incidents over time and correlate this number with the adoption of chaos engineering. The expectation is that the rate of severe incidents will decline. + * **Reduced incident rate** ‒ Track the number of production incidents over time and correlate this number with the adoption of chaos engineering. The expectation is that the rate of severe incidents will decline. @@ -87 +87 @@ To track progress in chaos engineering over time, capture the following metrics - * **Improved mean time to resolution (MTTR)** – Calculate the average time it takes to resolve incidents and track this data to see if it improves with chaos engineering over time. + * **Improved mean time to resolution (MTTR)** ‒ Calculate the average time it takes to resolve incidents and track this data to see if it improves with chaos engineering over time. @@ -89 +89 @@ To track progress in chaos engineering over time, capture the following metrics - * **Increased application availability** – Use service-level metrics to show availability improvements as application resilience increases through chaos experiments. + * **Increased application availability** ‒ Use service-level metrics to show availability improvements as application resilience increases through chaos experiments. @@ -91 +91 @@ To track progress in chaos engineering over time, capture the following metrics - * **Faster time to market** – Chaos engineering can provide the confidence to launch innovative offerings faster, because you know that your applications are resilient. Track increases in product release velocity. + * **Faster time to market** ‒ Chaos engineering can provide the confidence to launch innovative offerings faster, because you know that your applications are resilient. Track increases in product release velocity. @@ -93 +93 @@ To track progress in chaos engineering over time, capture the following metrics - * **Operational cost reduction** – Quantify if indicators such as alert noise, operational load, and manual effort to manage applications decrease with chaos practices in place. + * **Operational cost reduction** ‒ Quantify if indicators such as alert noise, operational load, and manual effort to manage applications decrease with chaos practices in place. @@ -95 +95 @@ To track progress in chaos engineering over time, capture the following metrics - * **Boosting confidence** – Survey developers, site reliability engineers (SREs), and other technical staff to gauge if chaos engineering boosted their confidence in application resilience. Perceptions matter. + * **Boosting confidence** ‒ Survey developers, site reliability engineers (SREs), and other technical staff to gauge if chaos engineering boosted their confidence in application resilience. Perceptions matter.