AWS dms documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the document for terminology consistency
Security assessment
The changes are purely terminological, removing the 'AWS' prefix from 'Direct Connect' service references. No security implications or modifications to security controls are evident in the changes.
Diff
diff --git a/dms/latest/userguide/instance-profiles-network.md b/dms/latest/userguide/instance-profiles-network.md index 06860bd51..077529bd3 100644 --- a//dms/latest/userguide/instance-profiles-network.md +++ b//dms/latest/userguide/instance-profiles-network.md @@ -5 +5 @@ -Single VPC configurationMultiple VPC configurationUsing AWS Direct Connect or a VPNUsing an internet connection +Single VPC configurationMultiple VPC configurationUsing Direct Connect or a VPNUsing an internet connection @@ -19 +19 @@ You can use different network configurations to set up interaction for your sour - * 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 @@ -40 +40 @@ To implement VPC peering, follow the instructions in [Work with VPC peering conn -## 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 @@ -42 +42 @@ To implement VPC peering, follow the instructions in [Work with VPC peering conn -Remote networks can connect to a VPC using several options, such as AWS Direct Connect or a software or hardware VPN connection. You can use these options to integrate existing on-site services by extending an internal network into the AWS Cloud. You might integrate on-site services such as monitoring, authentication, security, data, or other systems. By using this type of network extension, you can seamlessly connect on-site services to resources hosted by AWS, such as a VPC. You can use this configuration to convert your source on-premises database. +Remote networks can connect to a VPC using several options, such as Direct Connect or a software or hardware VPN connection. You can use these options to integrate existing on-site services by extending an internal network into the AWS Cloud. You might integrate on-site services such as monitoring, authentication, security, data, or other systems. By using this type of network extension, you can seamlessly connect on-site services to resources hosted by AWS, such as a VPC. You can use this configuration to convert your source on-premises database. @@ -48 +48 @@ In this configuration, the VPC security group must include a routing rule that s -If you don't use a VPN or AWS Direct Connect to connect to AWS resources, you can use an internet connection. This configuration involves a private subnet in a VPC with an internet gateway. The gateway contains the target data provider and the instance profile. You can use this configuration to convert your source on-premises database. +If you don't use a VPN or Direct Connect to connect to AWS resources, you can use an internet connection. This configuration involves a private subnet in a VPC with an internet gateway. The gateway contains the target data provider and the instance profile. You can use this configuration to convert your source on-premises database.