AWS dms documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in private replication instance documentation
Security assessment
The change only standardizes product naming conventions. No security controls or configurations were modified, and there's no evidence of security issue remediation.
Diff
diff --git a/dms/latest/userguide/CHAP_ReplicationInstance.PublicPrivate.md b/dms/latest/userguide/CHAP_ReplicationInstance.PublicPrivate.md index ba39ba94a..9ff0eab6f 100644 --- a//dms/latest/userguide/CHAP_ReplicationInstance.PublicPrivate.md +++ b//dms/latest/userguide/CHAP_ReplicationInstance.PublicPrivate.md @@ -9 +9 @@ You can specify if a replication instance has a public or private IP address tha -A _private replication instance_ has a private IP address that you can't access outside the replication network. You use a private instance when both source and target databases are in the same network that is connected to the virtual private cloud (VPC) of the replication instance. The network can be connected to the VPC by using a virtual private network (VPN), AWS Direct Connect, or VPC peering. +A _private replication instance_ has a private IP address that you can't access outside the replication network. You use a private instance when both source and target databases are in the same network that is connected to the virtual private cloud (VPC) of the replication instance. The network can be connected to the VPC by using a virtual private network (VPN), Direct Connect, or VPC peering.