AWS prescriptive-guidance documentation change
Summary
Updated navigation links, corrected punctuation, modified image paths, added 'AWS' to Storage Gateway references, and changed page title
Security assessment
Changes are cosmetic (punctuation fixes), navigational (link updates), or branding-related (adding 'AWS' to product names). No security vulnerabilities, configurations, or features are discussed or modified. Image path changes don't impact security content.
Diff
diff --git a/prescriptive-guidance/latest/backup-recovery/on-prem-dr-to-aws.md b/prescriptive-guidance/latest/backup-recovery/on-prem-dr-to-aws.md index 1bab096b8..e999c9874 100644 --- a//prescriptive-guidance/latest/backup-recovery/on-prem-dr-to-aws.md +++ b//prescriptive-guidance/latest/backup-recovery/on-prem-dr-to-aws.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) @@ -13 +13 @@ There are a number of options available to help you quickly set up and provision -AWS provides [AWS Elastic Disaster Recovery](https://docs.aws.amazon.com/drs/latest/userguide/what-is-drs.html) for creating a full replica of your on-premises servers, including the root volume and operating system, on AWS. Elastic Disaster Recovery continuously replicates your machines into a low-cost staging area in your target AWS account and preferred AWS Region. The block level replication is an exact replica of your servers’ storage including the operating system, system state configuration, databases, applications, and files. If there is a disaster, you can instruct Elastic Disaster Recovery to quickly launch thousands of your machines in their fully provisioned state within minutes. +AWS provides [AWS Elastic Disaster Recovery](https://docs.aws.amazon.com/drs/latest/userguide/what-is-drs.html) for creating a full replica of your on-premises servers, including the root volume and operating system, on AWS. Elastic Disaster Recovery continuously replicates your machines into a low-cost staging area in your target AWS account and preferred AWS Region. The block level replication is an exact replica of your servers' storage including the operating system, system state configuration, databases, applications, and files. If there is a disaster, you can instruct Elastic Disaster Recovery to quickly launch thousands of your machines in their fully provisioned state within minutes. @@ -17 +17 @@ Elastic Disaster Recovery uses an agent installed on each of your on-premises se - + @@ -30 +30 @@ Elastic Disaster Recovery uses an agent installed on each of your on-premises se -It’s important to test the DR process and to verify that the live staging environment doesn’t create conflicts with the on-premises environment. For example, confirm that the appropriate licenses are available and functioning in your on-premises, staging, and initiated DR environment. Also confirm that any worker type processes that might poll and pull work from a central database are configured appropriately to avoid overlaps or conflicts. In your DR process, include any necessary steps that must be performed before your recovery server instances come online. Also include the steps to perform after the recovery server instances are online and available. You can use solutions such as the [AWS Elastic Disaster Recovery Plan Automation solution](https://github.com/aws-samples/drs-tools/tree/main/drs-plan-automation) or another approach to help you automate your DR plans. +It's important to test the DR process and to verify that the live staging environment doesn't create conflicts with the on-premises environment. For example, confirm that the appropriate licenses are available and functioning in your on-premises, staging, and initiated DR environment. Also confirm that any worker type processes that might poll and pull work from a central database are configured appropriately to avoid overlaps or conflicts. In your DR process, include any necessary steps that must be performed before your recovery server instances come online. Also include the steps to perform after the recovery server instances are online and available. You can use solutions such as the [AWS Elastic Disaster Recovery Plan Automation solution](https://github.com/aws-samples/drs-tools/tree/main/drs-plan-automation) or another approach to help you automate your DR plans. @@ -32 +32 @@ It’s important to test the DR process and to verify that the live staging envi -You can use a [Storage Gateway volume gateway](https://docs.aws.amazon.com/storagegateway/latest/userguide/managing-volumes.html) to provide your on-premises servers with cloud-based volumes. These volumes can also be quickly provisioned for use with Amazon EC2 using Amazon EBS snapshots. In particular, stored volume gateways provide your on-premises applications with low-latency access to their entire datasets. The volume gateways also provide durable snapshot-based backups that can be restored for on premises use or for use with Amazon EC2. You can schedule point-in-time snapshots based on the recovery point objective (RPO) for your workload. +You can use an [AWS Storage Gateway volume gateway](https://docs.aws.amazon.com/storagegateway/latest/userguide/managing-volumes.html) to provide your on-premises servers with cloud-based volumes. These volumes can also be quickly provisioned for use with Amazon EC2 using Amazon EBS snapshots. In particular, stored volume gateways provide your on-premises applications with low-latency access to their entire datasets. The volume gateways also provide durable snapshot-based backups that can be restored for on premises use or for use with Amazon EC2. You can schedule point-in-time snapshots based on the recovery point objective (RPO) for your workload. @@ -46 +46 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Disaster recovery +Disaster recovery with AWS