AWS dms documentation change
Summary
Updated network configuration guidance for RDS and on-premises database connections
Security assessment
The changes provide more flexible subnet configuration advice but do not address security vulnerabilities or introduce new security features. The NAT gateway reference relates to standard network configuration rather than security remediation.
Diff
diff --git a/dms/latest/userguide/instance-profiles.md b/dms/latest/userguide/instance-profiles.md index 1c7e2994e..73cbd087a 100644 --- a//dms/latest/userguide/instance-profiles.md +++ b//dms/latest/userguide/instance-profiles.md @@ -23 +23 @@ You can create multiple instance profiles in the AWS DMS console. Make sure that -To connect to Amazon RDS databases, use a subnet group that includes public subnets. To connect to on-premises databases, use a subnet group that includes private subnets. Make sure that you configured your network so that AWS DMS can access your source on-premises database using the NAT gateway's public IP address. For more information, see [Create a VPC based on Amazon VPC](./set-up.html#set-up-vpc). +To connect to Amazon RDS databases, use the subnet configuration appropriate for your RDS setup, whether public or private. For connecting to on-premises databases, If use a private subnet group and ensure that your network is configured to allow AWS DMS access to the source on-premises database through the NAT gateway's public IP address. For more information, see [Create a VPC based on Amazon VPC](./set-up.html#set-up-vpc).