AWS prescriptive-guidance documentation change
Summary
Updated navigation link, fixed apostrophe formatting, and added step numbering to two section headers.
Security assessment
Changes are cosmetic/structural without altering security guidance. Step numbering improves readability but doesn't introduce new security information.
Diff
diff --git a/prescriptive-guidance/latest/security-best-practices/test.md b/prescriptive-guidance/latest/security-best-practices/test.md index b1a55fed3..9b17d0ad1 100644 --- a//prescriptive-guidance/latest/security-best-practices/test.md +++ b//prescriptive-guidance/latest/security-best-practices/test.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Top 10 security best practices for securing backups in AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Top 10 security best practices for securing backups in AWS](introduction.html) @@ -15 +15 @@ You can start your data recovery workflow by establishing data recovery patterns -If you don’t frequently test such restore operations, you might find that your assumptions on AWS KMS encryption for cross-account, cross-Region operations are incorrect. Often, the only backup recovery pattern that actually works is the path you test frequently. Through routine testing of supported backup resource types, you can spot early warnings that could potentially cause future disturbances and loss of critical data. If possible, maintain a limited but feasible number of recovery paths and patterns to prevent wasted storage space, optimize costs, and save time. Fixing the problem when a recovery test fails is easier than losing valuable or critical data. +If you don't frequently test such restore operations, you might find that your assumptions on AWS KMS encryption for cross-account, cross-Region operations are incorrect. Often, the only backup recovery pattern that actually works is the path you test frequently. Through routine testing of supported backup resource types, you can spot early warnings that could potentially cause future disturbances and loss of critical data. If possible, maintain a limited but feasible number of recovery paths and patterns to prevent wasted storage space, optimize costs, and save time. Fixing the problem when a recovery test fails is easier than losing valuable or critical data. @@ -23 +23 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Audit backup configuration +Step 8. Audit backup configuration @@ -25 +25 @@ Audit backup configuration -Incident response plan +Step 10. Incorporate backup in your incident response plan