AWS mgn documentation change
Summary
Multiple wording changes replacing 'the following' with 'these' in requirements and permissions sections, and minor formatting adjustments in command/flag documentation
Security assessment
Changes are grammatical improvements and phrasing simplifications. While some sections discuss security practices (like permissions and update responsibilities), the edits don't introduce new security content or address vulnerabilities.
Diff
diff --git a/mgn/latest/ug/installing-vcenter-appliance-mgn.md b/mgn/latest/ug/installing-vcenter-appliance-mgn.md index 85cdb9013..9d6ae1b37 100644 --- a/mgn/latest/ug/installing-vcenter-appliance-mgn.md +++ b/mgn/latest/ug/installing-vcenter-appliance-mgn.md @@ -29 +29 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client requires the following 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 following additional permission must be provided: **Toggle disk change tracking**. + * 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.. @@ -49 +49 @@ Ensure that you review the notes below prior to installing the Application Migra - * The VM on which the Application Migration Service vCenter Client is installed should meet the following RAM, CPU, and memory requirements: + * The VM on which the Application Migration Service vCenter Client is installed should meet these RAM, CPU, and memory requirements: @@ -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 the following 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 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). @@ -86 +86 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client can be installed on the following 64 bit Linux versions: + * The Application Migration Service vCenter Client can be installed on these 64 bit Linux versions: @@ -96 +96 @@ Ensure that you review the notes below prior to installing the Application Migra - * The following flags are used by the installer: + * These flags are used by the installer: