AWS mgn documentation change
Summary
Minor grammatical improvements and rephrasing for clarity
Security assessment
Changes involve only grammatical improvements without altering security content. The documentation still describes the same secured network setup using PrivateLink and private IPs.
Diff
diff --git a/mgn/latest/ug/mgn-connector-installing-secured-network.md b/mgn/latest/ug/mgn-connector-installing-secured-network.md index fbcf33fb0..44e5253e4 100644 --- a//mgn/latest/ug/mgn-connector-installing-secured-network.md +++ b//mgn/latest/ug/mgn-connector-installing-secured-network.md @@ -21 +21 @@ If you are using the [Global view](./global-view.html) feature, which provides c -You will also need to designate a VPC in the management account in order to allow the MGN connector to communicate with AWS services via PrivateLink. If you are migrating some of your source servers into the management account, you can use the same VPC as a staging VPC. +You will also need to designate a VPC in the management account to allow the MGN connector to communicate with AWS services via PrivateLink. If you are migrating some of your source servers into the management account, you can use the same VPC as a staging VPC. @@ -86 +86 @@ For more information, see [ Forwarding inbound DNS queries to your VPCs ](https: -In order to allow the AWS Replication Agent to communicate with the replication server without using the public internet, you must use Private IP for data replication. The replication server requires access to the EC2 service. Therefore: +To allow the AWS Replication Agent to communicate with the replication server without using the public internet, you must use Private IP for data replication. The replication server requires access to the EC2 service. Therefore: