AWS resilience-hub: Restructure failure mode guidance overview
Summary
Rewrites the failure mode guidance page to describe assertions and service design files as the two forms of guidance, with links to dedicated topics.
Security assessment
Editorial restructuring of guidance documentation; no security feature, control, or vulnerability is involved.
Evidence
+A failure mode assessment can observe how your resources are configured and connected, but it cannot observe how your service is used, operated, or intended to behave. With failure mode guidance, you can supply that missing context. The assessment then produces failure mode findings that are relevant to your service. Next generation Resilience Hub supports two forms of failure mode guidance:
Diff
diff --git a/resilience-hub/latest/userguide/next-gen-failure-mode-guidance.md b/resilience-hub/latest/userguide/next-gen-failure-mode-guidance.md index 1663cc357..d154fac71 100644 --- a//resilience-hub/latest/userguide/next-gen-failure-mode-guidance.md +++ b//resilience-hub/latest/userguide/next-gen-failure-mode-guidance.md @@ -9 +9 @@ -Failure mode guidance allows you to steer the agents to dial in the failure mode analysis. +A failure mode assessment can observe how your resources are configured and connected, but it cannot observe how your service is used, operated, or intended to behave. With failure mode guidance, you can supply that missing context. The assessment then produces failure mode findings that are relevant to your service. Next generation Resilience Hub supports two forms of failure mode guidance: @@ -11 +11 @@ Failure mode guidance allows you to steer the agents to dial in the failure mode -**Assertions** + * **Assertions** – Short statements of fact about your service that the assessment treats as true. For more information, see [Assertions](./next-gen-assertions.html). @@ -13 +13 @@ Failure mode guidance allows you to steer the agents to dial in the failure mode -Assertions are statements about your application that provide context for failure mode assessments. They help the generative AI agents understand aspects of your architecture that are not visible from resource configuration alone. + * **Service design files** – Architecture documents stored in Amazon S3 that describe your intended design. For more information, see [Service design files](./next-gen-service-design-files.html). @@ -15 +14,0 @@ Assertions are statements about your application that provide context for failur -Assertions can be: @@ -17 +15,0 @@ Assertions can be: - * **User-created** – You add assertions before running an assessment. Examples include "Data loss is unacceptable," "Traffic spikes are predictable," or "Typical traffic is 1,000 TPS spiking to 10,000 TPS." @@ -19 +16,0 @@ Assertions can be: - * **System-generated** – The assessment engine generates assertions during analysis that you can review, confirm, or adjust. @@ -20,0 +18 @@ Assertions can be: +###### Topics @@ -21,0 +20 @@ Assertions can be: + * [Assertions](./next-gen-assertions.html) @@ -22,0 +22 @@ Assertions can be: + * [Service design files](./next-gen-service-design-files.html) @@ -24 +23,0 @@ Assertions can be: -Assertions are categorized and serve as leverage points. By confirming or adjusting assertions, you steer the assessment toward more relevant findings. For example, if the assessment assumes your application must handle 100 TPS, but it actually needs to handle spikes of 10,000 TPS, adjusting that assertion changes the findings you receive. @@ -26 +24,0 @@ Assertions are categorized and serve as leverage points. By confirming or adjust -**Service design files** @@ -28 +25,0 @@ Assertions are categorized and serve as leverage points. By confirming or adjust -You can upload design files that include details about the technical design that will be provided to the AI agents to perform the failure mode analysis. @@ -38 +35 @@ Relationship to resilience policies -Running a failure mode assessment at the service level +Assertions