AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation, capitalized 'Design' in stage reference, changed 'AWS Well-Architected Framework' to 'AWS Well-Architected', and removed redundant phrase 'caused during that event'.
Security assessment
Changes are editorial improvements and terminology updates without addressing security vulnerabilities or weaknesses. No security-specific content was added or modified.
Diff
diff --git a/prescriptive-guidance/latest/resilience-lifecycle-framework/stage-1.md b/prescriptive-guidance/latest/resilience-lifecycle-framework/stage-1.md index 0fe6c0b3a..177b21b3b 100644 --- a//prescriptive-guidance/latest/resilience-lifecycle-framework/stage-1.md +++ b//prescriptive-guidance/latest/resilience-lifecycle-framework/stage-1.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Resilience lifecycle framework](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Resilience lifecycle framework: A continuous approach to resilience improvement](introduction.html) @@ -15 +15 @@ Not all applications need the same level of resilience. When you set objectives, -After you define objectives, you implement observability controls in later stages ([Stage 2: design and implement](./stage-2.html) and [Stage 4: Operate](./stage-4.html)) to understand if the objectives are being met. +After you define objectives, you implement observability controls in later stages ([Stage 2: Design and implement](./stage-2.html) and [Stage 4: Operate](./stage-4.html)) to understand if the objectives are being met. @@ -37 +37 @@ SLO metrics are commonly used in the definition of service-level agreements (SLA -You can start to set your objectives based on SLOs, RPOs, and RTOs. After you define your resilience objectives and gain a clear understanding of your RPO and RTO targets, you can use [AWS Resilience Hub](https://aws.amazon.com/resilience-hub/) to run an assessment of your architecture to uncover potential resilience-related weaknesses. AWS Resilience Hub assesses an application architecture against AWS Well-Architected Framework best practices and shares remediation guidance in the context of what specifically needs to be improved to meet your defined RTO and RPO targets. +You can start to set your objectives based on SLOs, RPOs, and RTOs. After you define your resilience objectives and gain a clear understanding of your RPO and RTO targets, you can use [AWS Resilience Hub](https://aws.amazon.com/resilience-hub/) to run an assessment of your architecture to uncover potential resilience-related weaknesses. AWS Resilience Hub assesses an application architecture against AWS Well-Architected best practices and shares remediation guidance in the context of what specifically needs to be improved to meet your defined RTO and RPO targets. @@ -43 +43 @@ RPO, RTO and SLOs are good indicators of resilience, but you can also think abou -If you think about the objective to continue operating if you lose 5% of the instances that power your application, you might determine that your application should be prescaled or have the ability to scale fast enough to support the additional traffic caused during that event. Or, you might determine that you should leverage different architectural patterns, as described in the [Stage 2: Design and implement](./stage-2.html) section. +If you think about the objective to continue operating if you lose 5% of the instances that power your application, you might determine that your application should be prescaled or have the ability to scale fast enough to support the additional traffic . Or, you might determine that you should leverage different architectural patterns, as described in the [Stage 2: Design and implement](./stage-2.html) section.