AWS drs medium security documentation change
Summary
Minor grammatical updates and tense corrections throughout. Fixed broken link for 'Use private ip' documentation (link target removed).
Security assessment
The removal of the valid link to 'Use private ip' documentation (now an empty link) may hinder users' ability to properly configure private IP routing, potentially leading to unintended use of public subnets. This could expose replication servers to public networks by default if users don't manually locate the correct security guidance.
Diff
diff --git a/drs/latest/userguide/individual-replication-settings.md b/drs/latest/userguide/individual-replication-settings.md index d5fa4e9de..f05748ee1 100644 --- a//drs/latest/userguide/individual-replication-settings.md +++ b//drs/latest/userguide/individual-replication-settings.md @@ -9 +9 @@ Replication server configuration -AWS Elastic Disaster Recovery will attempt to help save you costs by consolidating the replication of as many source servers as possible onto the same Replication Server based on the individual Source Server **Replication Settings**. Source Servers must have identical **Replication Settings** to be considered for consolidation, and must not have Use dedicated replication instance enabled. For example, DRS will not consolidate Source Servers that have a different **Staging area subnet** specified in their **Replication Settings**. To reduce EC2 usage, we recommend having as many as possible Source Servers have identical **Replication Settings** to one another. +AWS Elastic Disaster Recovery attempts to reduce costs by consolidating the replication of as many source servers as possible onto the same Replication Server based on the individual Source Server **Replication Settings**. Source Servers must have identical **Replication Settings** to be considered for consolidation, and must not have Use dedicated replication instance enabled. For example, DRS does not consolidate Source Servers that have a different **Staging area subnet** specified in their **Replication Settings**. To reduce EC2 usage, we recommend having as many as possible Source Servers have identical **Replication Settings** to one another. @@ -31 +31 @@ Replication Servers are AWS EC2 Instances automatically launched by AWS Elastic -The **Staging area subnet** setting defines which VPC Subnet that the a Replication Server for a Source Server will use. A Source Server must be able to successfully initialize connections to the subnet configured within its **Staging area subnet** setting. The best practice is to create a single dedicated, separate subnet for recovery in your AWS Account. Learn more about creating subnets in [this AWS VPC article](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html). Unless [Use private ip](./data-routing.html#use-private-ip) is enabled and valid routing within the VPC exists, Replication Servers must be in a [Public subnet](https://docs.aws.amazon.com/vpc/latest/userguide/configure-subnets.html#subnet-types). By default, a Replication Servers will assign itself a [Public IPv4](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses) without any additional configuration needed. +The **Staging area subnet** setting defines which VPC Subnet that the a Replication Server for a Source Server uses. A Source Server must be able to successfully initialize connections to the subnet configured within its **Staging area subnet** setting. The best practice is to create a single dedicated, separate subnet for recovery in your AWS Account. Learn more about creating subnets in [this AWS VPC article](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html). Unless [Use private ip]() is enabled and valid routing within the VPC exists, Replication Servers must be in a [Public subnet](https://docs.aws.amazon.com/vpc/latest/userguide/configure-subnets.html#subnet-types). By default, a Replication Servers assigns itself a [Public IPv4](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses) without any additional configuration needed. @@ -73 +73 @@ Command Line -The **Replication server instance type** will determine the EC2 Instance type and size that will be used for the launch of a source server's replication server. DRS Replicators only support EC2 Instances with x86_64 CPU architecture. +The **Replication server instance type** determines the EC2 Instance type and size that is used for the launch of a source server's replication server. DRS Replicators only support EC2 Instances with x86_64 CPU architecture. @@ -119 +119 @@ Command Line -The **Dedicated instance for replication server** setting specifies whether or not the Source Server's can use to a Replication Server shared with other Source Servers. By default, AWS Elastic Disaster Recovery will attempt to consolidate as many Source Servers as possible onto a single Replication Server, based on a variety of factors. Setting **Dedicated instance for replication server** to **use dedicated replication instance** will ensure only this Source Server will replicate data to the Replication Server. +The **Dedicated instance for replication server** setting specifies whether or not the Source Server's can use to a Replication Server shared with other Source Servers. By default, AWS Elastic Disaster Recovery attempts to consolidate as many Source Servers as possible onto a single Replication Server, based on a variety of factors. Setting **Dedicated instance for replication server** to **use dedicated replication instance** ensures that only this Source Server replicates data to the Replication Server.