AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, replaced 'RTO/RPO' spelled-out terms with acronyms, standardized hyphenation in 'data-level', and refined sidebar titles.
Security assessment
Changes are purely editorial and navigational. No security implications exist as backup strategy principles remain unchanged without vulnerability references.
Diff
diff --git a/prescriptive-guidance/latest/backup-recovery/design.md b/prescriptive-guidance/latest/backup-recovery/design.md index 7ea6c06a2..8fb7c3350 100644 --- a//prescriptive-guidance/latest/backup-recovery/design.md +++ b//prescriptive-guidance/latest/backup-recovery/design.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Backup and recovery approaches on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Backup and recovery approaches on AWS](introduction.html) @@ -11 +11 @@ When developing a comprehensive strategy for backing up and restoring data, you -Backup and recovery processes should include the appropriate level of granularity to meet recovery time objective (RTO) and recovery point objective (RPO) for the workload and its supporting business processes, including the following: +Backup and recovery processes should include the appropriate level of granularity to meet RTO and RPO for the workload and its supporting business processes, including the following: @@ -15 +15 @@ Backup and recovery processes should include the appropriate level of granularit - * Application data–level recovery (for example, a specific database within MySQL) + * Application data-level recovery (for example, a specific database within MySQL) @@ -30 +30 @@ Be sure to consider all the recovery requirements for your solution and the data -The following topics describe backup and recovery approaches based on the organization of your infrastructure. IT infrastructure can broadly be categorized as on-premises, hybrid, or cloud native. +The following sections describe backup and recovery approaches based on the organization of your infrastructure. IT infrastructure can broadly be categorized as on-premises, hybrid, or cloud native. @@ -38 +38 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Choosing AWS services +Choosing AWS services for data protection @@ -40 +40 @@ Choosing AWS services -AWS Backup +Backup and recovery using AWS Backup