AWS mgn documentation change
Summary
Updated phrasing for clarity and accuracy, removed direct VDDK download link in favor of Broadcomm account reference
Security assessment
Changes focus on grammatical improvements and vendor reference updates. Certificate-related notes about permissions and hostname usage reinforce existing security practices but don't address new vulnerabilities or add security documentation.
Diff
diff --git a/mgn/latest/ug/client-installation-instructions-mgn.md b/mgn/latest/ug/client-installation-instructions-mgn.md index e9ab1568e..fe2d8b6ca 100644 --- a//mgn/latest/ug/client-installation-instructions-mgn.md +++ b//mgn/latest/ug/client-installation-instructions-mgn.md @@ -35 +35 @@ This is an example of the installer hash link for us-east-1: `https://aws-applic - 4. The installer will then prompt you to enter your vCenter information, enter the required info in each field and then press **Enter** : + 4. The installer then prompts you to enter your vCenter information, enter the required info in each field and then press **Enter** : @@ -51 +51 @@ This is an example of the installer hash link for us-east-1: `https://aws-applic - * The certificate must be located in a file that's readable to the vCenter client user, such as a shared directory. If the certificate is not located in a shared directory, you will see a permission error in the logs (Error 13). + * The certificate must be located in a file that's readable to the vCenter client user, such as a shared directory. If the certificate is not located in a shared directory, you see a permission error in the logs (Error 13). @@ -53 +53 @@ This is an example of the installer hash link for us-east-1: `https://aws-applic - * To use a certificate in your vCenter environment, you must setup a connection using a hostname. Using an IP will not work with a certificate. + * To use a certificate in your vCenter environment, you must setup a connection using a hostname. Using an IP does not work with a certificate. @@ -57 +57 @@ This is an example of the installer hash link for us-east-1: `https://aws-applic - * Path to VDDK tarball - Provide the path to the [VDDK tarball](https://customerconnect.vmware.com/downloads/get-download?downloadGroup=VDDK7033) you previously downloaded onto the VM. (example: `path/to/VMware-vix-disklib-7.0.3-21933544.x86_64.tar.gz`) + * Path to VDDK tarball - Provide the path to the VDDK tarball that you previously downloaded onto the VM. (example: `path/to/VMware-vix-disklib-7.0.3-21933544.x86_64.tar.gz`). You can download VDDK tarball from your Broadcomm account. @@ -67 +67 @@ KEY=VALUE [KEY=VALUE ...] add resource tags to the source servers added by disco - 5. The installer will proceed to download and install the AWS vCenter client and will register it with AWS Application Migration Service. + 5. The installer downloads and installs the AWS vCenter client and registers it with AWS Application Migration Service. @@ -71 +71 @@ KEY=VALUE [KEY=VALUE ...] add resource tags to the source servers added by disco - 6. Once the AWS vCenter client has been installed, all of the VMs in your vCenter will be added to AWS Application Migration Service. The VMs will be added in the DISCOVERED state. + 6. Once the AWS vCenter client has been installed, all of the VMs in your vCenter are added to AWS Application Migration Service. The VMs are added in the DISCOVERED state. @@ -75 +75 @@ KEY=VALUE [KEY=VALUE ...] add resource tags to the source servers added by disco - * If you have a significant amount of VMs in your vCenter environment, it may take some time for all of the VMs to become visible in the Application Migration Service Console. + * If you have a significant amount of VMs in your vCenter environment, it may take some time for all of the VMs to become visible in the Application Migration Service console.