AWS dms documentation change
Summary
Updated reference from 'AWS Direct Connect' to 'Direct Connect' in security configuration documentation
Security assessment
Similar to the first file, this change only modifies service naming conventions without altering any security requirements, configurations, or recommendations. The security group rules and network architecture descriptions remain unchanged, indicating no direct security impact.
Diff
diff --git a/dms/latest/userguide/CHAP_Security.md b/dms/latest/userguide/CHAP_Security.md index 4b09ca019..ab69e6467 100644 --- a//dms/latest/userguide/CHAP_Security.md +++ b//dms/latest/userguide/CHAP_Security.md @@ -220 +220 @@ The network configurations that you can use for database migration each require - * [ Configuration for a network to a VPC using AWS Direct Connect or a VPN](./CHAP_ReplicationInstance.VPC.html#CHAP_ReplicationInstance.VPC.Configurations.ScenarioDirect) – a VPN tunnel allowing traffic to tunnel from the VPC into an on- premises VPN. In this configuration, the VPC includes a routing rule that sends traffic destined for a specific IP address or range to a host that can bridge traffic from the VPC into the on-premises VPN. If this case, the NAT host includes its own Security Group settings that must allow traffic from the Replication Instance's private IP address or security group into the NAT instance. + * [ Configuration for a network to a VPC using Direct Connect or a VPN](./CHAP_ReplicationInstance.VPC.html#CHAP_ReplicationInstance.VPC.Configurations.ScenarioDirect) – a VPN tunnel allowing traffic to tunnel from the VPC into an on- premises VPN. In this configuration, the VPC includes a routing rule that sends traffic destined for a specific IP address or range to a host that can bridge traffic from the VPC into the on-premises VPN. If this case, the NAT host includes its own Security Group settings that must allow traffic from the Replication Instance's private IP address or security group into the NAT instance.