AWS mgn documentation change
Summary
Multiple grammatical and phrasing improvements. Updated VDDK download instructions to specify Broadcomm account login. Clarified security responsibilities when disabling auto-updates.
Security assessment
Changes are primarily grammatical improvements and procedural clarifications. The VDDK download instruction update reflects a vendor process change but doesn't explicitly address a security vulnerability. The auto-update clarification reiterates existing security responsibilities rather than introducing new security documentation.
Diff
diff --git a/mgn/latest/ug/installing-vcenter-appliance-mgn.md b/mgn/latest/ug/installing-vcenter-appliance-mgn.md index 9d6ae1b37..bca61e1cb 100644 --- a//mgn/latest/ug/installing-vcenter-appliance-mgn.md +++ b//mgn/latest/ug/installing-vcenter-appliance-mgn.md @@ -13 +13 @@ The first step to deploying the agentless solution is installing the Application -If you have multiple vCenter environments, you will need to install multiple clients. You may not have more than one Application Migration Service vCenter Client installed per AWS account. If you have multiple vCenter environments, you can either use a different AWS account for each environment or you can migrate your VMs serially, environment by environment, into the same AWS account. +If you have multiple vCenter environments, you need to install multiple clients. You may not have more than one Application Migration Service vCenter Client installed per AWS account. If you have multiple vCenter environments, you can either use a different AWS account for each environment or you can migrate your VMs serially, environment by environment, into the same AWS account. @@ -15 +15 @@ If you have multiple vCenter environments, you will need to install multiple cli -After the Application Migration Service vCenter Client has been installed, it will discover all of the VMs in your vCenter environment and add them to Application Migration Service. +After the Application Migration Service vCenter Client has been installed, it discovers all of the VMs in your vCenter environment and add them to Application Migration Service. @@ -25 +25 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client currently only supports VirtualDiskFlatVer2BackingInfo VMDK on CBT. [Learn more about this in the VMware knowledgebase.](https://vdc-repo.vmware.com/vmwb-repository/dcr-public/89853aba-2fc4-4ad1-beb8-9451f02ac6b2/670d8b74-3ddd-4142-aa16-6fef1961db8a/GUID-9992FD61-1D92-4CA2-937D-2DE47DDD27D2.html) + * The Application Migration Service vCenter Client currently only supports VirtualDiskFlatVer2BackingInfo VMDK on CBT. @@ -27 +27 @@ Ensure that you review the notes below prior to installing the Application Migra - * You must download [this VDDK version](https://customerconnect.vmware.com/downloads/get-download?downloadGroup=VDDK7033) to the VM on which the Application Migration Service vCenter Client is installed. VDDK 7.0.3.3 must be used, regardless of the vCenter version used. + * You must log in to your Broadcomm account and download VDDK 7.0.3.3 to the VM on which the Application Migration Service vCenter Client is installed. VDDK 7.0.3.3 must be used, regardless of the vCenter version used. @@ -29 +29 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client requires these vCenter user permissions for agentless deployment. It is a best practice to create a dedicated role with these permissions and a dedicated user group with which the role will be associated. Every new user created for the Application Migration Service vCenter Client will need to be a member of that group in order to obtain the required permissions. The vCenter predefined role: “ Consolidated Backup user (sample) ” provides most of these permissions. If that role is used, the **Toggle disk change tracking** permission must be provided.. + * The Application Migration Service vCenter Client requires these vCenter user permissions for agentless deployment. It is a best practice to create a dedicated role with these permissions and a dedicated user group with which the role is associated. Every new user created for the Application Migration Service vCenter Client needs to be a member of that group in order to obtain the required permissions. The vCenter predefined role: “ Consolidated Backup user (sample) ” provides most of these permissions. If that role is used, the **Toggle disk change tracking** permission must be provided.. @@ -51 +51 @@ Ensure that you review the notes below prior to installing the Application Migra - * Minimal requirements (these requirements will allow the replication of up to 5 servers in parallel) – 2 GiB RAM, 1 core, 10 GiB of free disk space + * Minimal requirements (these requirements allow the replication of up to 5 servers in parallel) – 2 GiB RAM, 1 core, 10 GiB of free disk space @@ -53 +53 @@ Ensure that you review the notes below prior to installing the Application Migra - * Optional performance requirements (these requirements will allow the replication of the maximum number of 50 servers in parallel) – 16 GiB RAM, 8 cores, 10 GiB of free disk space + * Optional performance requirements (these requirements allow the replication of the maximum number of 50 servers in parallel) – 16 GiB RAM, 8 cores, 10 GiB of free disk space @@ -77 +77 @@ Ensure that you review the notes below prior to installing the Application Migra - * You can deactivate the vCenter Client auto-update mechanism by running this command: `touch /var/lib/aws-vcenter-client/.disable_auto_updates` Once auto-updates are deactivated, you will need to reinstall the client to perform a manual update. If you deactivate the auto-update mechanism, you will be responsible for ensuring that all security updates are performed on the client. After a manual update, you should validate the new hash against the [installer hash](./client-installation-instructions-mgn.html). + * You can deactivate the vCenter Client auto-update mechanism by running this command: `touch /var/lib/aws-vcenter-client/.disable_auto_updates` Once auto-updates are deactivated, you need to reinstall the client to perform a manual update. If you deactivate the auto-update mechanism, you are responsible for ensuring that all security updates are performed on the client. After a manual update, you should validate the new hash against the [installer hash](./client-installation-instructions-mgn.html). @@ -153 +153 @@ Optional arguments: - * Once added to Application Migration Service, snapshot-based replication will create snapshots on the replicated VM, which may result in slower disk performance. + * Once added to Application Migration Service, snapshot-based replication creates snapshots on the replicated VM, which may result in slower disk performance. @@ -157 +157 @@ Optional arguments: - * The VM being replicated into Application Migration Service can be either stopped or running. Changing the VM state during data replication will not affect data replication and will cause no data corruption. + * The VM being replicated into Application Migration Service can be either stopped or running. Changing the VM state during data replication does not affect data replication and causes no data corruption.