AWS drs: Fix bandwidth test link and 'Direct Connect' typo
Summary
Updates the network bandwidth test link to the new page and corrects a truncated sentence about public networks to read 'no VPN or Direct Connect'.
Security assessment
The edits are a documentation link update and a typo fix; the surrounding public-IP guidance is pre-existing and unchanged, so no new security posture is introduced.
Evidence
+ * If you use a public network (no VPN or Direct Connect), ensure the recovery instance has a public IP address. By default, Elastic Disaster Recovery launch templates disable public IP assignment.
Diff
diff --git a/drs/latest/userguide/replication-performance-errors.md b/drs/latest/userguide/replication-performance-errors.md index a5fe8ed..1a8841b 100644 --- a//drs/latest/userguide/replication-performance-errors.md +++ b//drs/latest/userguide/replication-performance-errors.md @@ -69 +69 @@ Additionally: - * Run a bandwidth test. For more information, see [network bandwidth test](./Replication-Related-FAQ.html#perform-connectivity-bandwidth-test). + * Run a bandwidth test. For more information, see [network bandwidth test](./network-bandwidth-test.html). @@ -170 +170 @@ Changing the staging disk type might affect replication costs. Review Amazon EBS - * If you use a public network (no VPN or ), ensure the recovery instance has a public IP address. By default, Elastic Disaster Recovery launch templates disable public IP assignment. + * If you use a public network (no VPN or Direct Connect), ensure the recovery instance has a public IP address. By default, Elastic Disaster Recovery launch templates disable public IP assignment.