AWS drs documentation change
Summary
Added IP version section documenting IPv6 support for data replication, including prerequisites and limitations
Security assessment
This change adds documentation for IPv6 support feature. While it mentions networking and connectivity, there's no evidence of addressing a specific security vulnerability or weakness. The change is primarily about feature documentation and IPv6 adoption.
Diff
diff --git a/drs/latest/userguide/data-routing.md b/drs/latest/userguide/data-routing.md index 3d332fe2f..e98de659a 100644 --- a//drs/latest/userguide/data-routing.md +++ b//drs/latest/userguide/data-routing.md @@ -0,0 +1,2 @@ +[View a markdown version of this page](data-routing.md) + @@ -5 +7 @@ -Throttle network bandwidth +IP versionThrottle network bandwidth @@ -9 +11 @@ Throttle network bandwidth -AWS Elastic Disaster Recovery lets you control how data is routed from your source servers to the replication servers on AWS through the **Data routing and throttling** settings. By default, data is sent from the source servers to the replication servers over the public internet, using the public IP that was automatically assigned to the replication servers. Transferred data is always encrypted in transit. Choose **Use private IP for data replication...** if you want to route the replicated data from your source servers to the staging area subnet through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection. Data replication does not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console. Use this option if you want to: +AWS Elastic Disaster Recovery lets you control how data is routed from your source servers to the replication servers on AWS through the **Data routing and throttling** settings. By default, data is sent from the source servers to the replication servers over the public internet, using the public IPv4 address that was automatically assigned to the replication servers. Transferred data is always encrypted in transit. Choose **Use private IP for data replication...** if you want to route the replicated data from your source servers to the staging area subnet through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection. Data replication does not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console. Use this option if you want to: @@ -32,0 +35,42 @@ AWS Elastic Disaster Recovery lets you control how data is routed from your sour +## IP version + +The **IP version** setting controls the Internet Protocol version that AWS Elastic Disaster Recovery uses for data replication and for communication between your source servers and the staging area. You can choose between **IPv4** (default) and **IPv6**. + +When you select **IPv6** , the following changes apply: + + * Data replication from the AWS Replication Agent to the replication server uses IPv6. + + * The replication server receives an IPv6 address and does not receive a public IPv4 address. + + * Communication during drills and recoveries uses IPv6. + + + + +###### Important + +Before you select **IPv6** , verify the following prerequisites: + + * Your staging area subnet must have an IPv6 CIDR block. + + * Your replication server instance type must support IPv6. + + + + +There is no automatic fallback to IPv4 for data replication. If IPv6 connectivity between your source servers and the replication servers is unavailable, data replication fails. + +###### Note + +When you select **IPv6** , other IP-related options (such as **Use private IP** and **Create public IP**) are hidden in the console. Your prior IPv4 configurations are preserved and take effect if you switch back to **IPv4**. + +###### Note + +The **IP version** setting does not affect recovery instance networking. Recovery instances use the networking configuration defined in your launch settings. + +###### Note + +If you use the Failback Client for failback to on-premises infrastructure, the Failback Client currently supports IPv4 only. In-AWS failback uses the configured IP version. + +The **IP version** setting is separate from the `--dualstack` installer parameter. The `--dualstack` parameter controls which API endpoints the agent uses to communicate with AWS services, and does not change the IP version used for data replication. For more information, see [AWS Replication Agent Installer parameters](./installer-parameters.html). +