AWS dms documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' in section headers and content, removing 'AWS' branding from the service name.
Security assessment
The changes are purely branding/naming updates (removing 'AWS' from 'AWS Direct Connect'). No security-related content was added, removed, or modified. The security implications of network configurations (e.g., VPC security groups, NAT instances) remain unchanged.
Diff
diff --git a/dms/latest/userguide/dm-network.md b/dms/latest/userguide/dm-network.md index 1a84a6f79..743237f91 100644 --- a//dms/latest/userguide/dm-network.md +++ b//dms/latest/userguide/dm-network.md @@ -5 +5 @@ -Single VPC configurationDifferent VPC configurationUsing AWS Direct ConnectResolving domain endpoints +Single VPC configurationDifferent VPC configurationUsing Direct ConnectResolving domain endpoints @@ -19 +19 @@ Also, for ongoing data replication, you must set up interaction between your sou - * Using AWS Direct Connect or a VPN to configure a network to a VPC + * Using Direct Connect or a VPN to configure a network to a VPC @@ -90 +90 @@ If you require a persistent public IP address that can be associated to the data -## Using AWS Direct Connect or a VPN to configure a network to a VPC +## Using Direct Connect or a VPN to configure a network to a VPC @@ -92 +92 @@ If you require a persistent public IP address that can be associated to the data -You can connect remote networks to your VPC through AWS Direct Connect or VPN connections (software or hardware). These options enable you to extend your internal network into AWS Cloud and integrate existing on-premises services such as monitoring, authentication, security, and data systems with your AWS resources. For this configuration, your VPC security group must include a routing rule that directs traffic to a host capable of bridging VPC traffic to your on-premises VPN. This traffic can be designated using either your VPC CIDR range or specific IP addresses. The NAT host must have its own security group configured to allow traffic from your VPC CIDR range or security group into the NAT instance, ensuring seamless communication between your VPC and on-premises infrastructure. For more information, see [step 5](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html#vpn-create-vpn-connection) for [Get started with AWS Site-to-Site VPN](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html#vpn-create-vpn-connection) procedure in the AWS Site-to-Site VPN User Guide. +You can connect remote networks to your VPC through Direct Connect or VPN connections (software or hardware). These options enable you to extend your internal network into AWS Cloud and integrate existing on-premises services such as monitoring, authentication, security, and data systems with your AWS resources. For this configuration, your VPC security group must include a routing rule that directs traffic to a host capable of bridging VPC traffic to your on-premises VPN. This traffic can be designated using either your VPC CIDR range or specific IP addresses. The NAT host must have its own security group configured to allow traffic from your VPC CIDR range or security group into the NAT instance, ensuring seamless communication between your VPC and on-premises infrastructure. For more information, see [step 5](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html#vpn-create-vpn-connection) for [Get started with AWS Site-to-Site VPN](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html#vpn-create-vpn-connection) procedure in the AWS Site-to-Site VPN User Guide.