AWS mgn documentation change
Summary
Renamed 'Application Migration Service' to 'MGN' or 'AWS Transform MGN' throughout the documentation
Security assessment
The changes are purely branding updates with no modifications to security requirements, configurations, or vulnerabilities. The existing security recommendations (network isolation, trusted access, egress restrictions) remain unchanged but now reference the new service name.
Diff
diff --git a/mgn/latest/ug/installing-vcenter-appliance-mgn.md b/mgn/latest/ug/installing-vcenter-appliance-mgn.md index 86262f2cb..57a051b67 100644 --- a//mgn/latest/ug/installing-vcenter-appliance-mgn.md +++ b//mgn/latest/ug/installing-vcenter-appliance-mgn.md @@ -5 +5 @@ -[Documentation](/index.html)[Application Migration Service](/mgn/index.html)[User Guide](what-is-mgn.html) +[Documentation](/index.html)[AWS Transform MGN](/mgn/index.html)[User Guide](what-is-mgn.html) @@ -7 +7 @@ -Application Migration Service vCenter Client requirements +MGN vCenter Client requirements @@ -11 +11 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -# Installing the Application Migration Service vCenter Client +# Installing the MGN vCenter Client @@ -13 +13 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -The first step to deploying the agentless solution is installing the Application Migration Service vCenter Client on your vCenter environment. +The first step to deploying the agentless solution is installing the MGN vCenter Client on your vCenter environment. @@ -17 +17 @@ The first step to deploying the agentless solution is installing the Application -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. +If you have multiple vCenter environments, you need to install multiple clients. You may not have more than one MGN 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. @@ -19 +19 @@ If you have multiple vCenter environments, you need to install multiple clients. -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. +After the MGN vCenter Client has been installed, it discovers all of the VMs in your vCenter environment and add them to MGN. @@ -21 +21 @@ After the Application Migration Service vCenter Client has been installed, it di -## Application Migration Service vCenter Client requirements +## MGN vCenter Client requirements @@ -23 +23 @@ After the Application Migration Service vCenter Client has been installed, it di -Ensure that you review the notes below prior to installing the Application Migration Service vCenter Client. Once you have read the notes, proceed to [install the client](./client-installation-instructions-mgn.html). +Ensure that you review the notes below prior to installing the MGN vCenter Client. Once you have read the notes, proceed to [install the client](./client-installation-instructions-mgn.html). @@ -27 +27 @@ Ensure that you review the notes below prior to installing the Application Migra - * You must install the Application Migration Service vCenter Client on a VM that has outbound network connectivity to the AWS Application Migration Service API endpoints and outbound network connectivity to the vCenter endpoint. Customers who want to use PrivateLink can use VPN or AWS Direct Connect to connect to AWS. + * You must install the MGN vCenter Client on a VM that has outbound network connectivity to the AWS Transform MGN API endpoints and outbound network connectivity to the vCenter endpoint. Customers who want to use PrivateLink can use VPN or AWS Direct Connect to connect to AWS. @@ -29 +29 @@ 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. + * The MGN vCenter Client currently only supports VirtualDiskFlatVer2BackingInfo VMDK on CBT. @@ -31 +31 @@ Ensure that you review the notes below prior to installing the Application Migra - * 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. + * You must log in to your Broadcomm account and download VDDK 7.0.3.3 to the VM on which the MGN vCenter Client is installed. VDDK 7.0.3.3 must be used, regardless of the vCenter version used. @@ -33 +33 @@ 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 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.. + * The MGN 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 MGN 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.. @@ -53 +53 @@ 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 these RAM, CPU, and memory requirements: + * The VM on which the MGN vCenter Client is installed should meet these RAM, CPU, and memory requirements: @@ -61 +61 @@ 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 not allow any incoming (ingress) traffic. + * The VM on which the MGN vCenter Client is installed should not allow any incoming (ingress) traffic. @@ -63 +63 @@ 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 only allow outgoing traffic as following: + * The VM on which the MGN vCenter Client is installed should only allow outgoing traffic as following: @@ -67 +67 @@ Ensure that you review the notes below prior to installing the Application Migra - * Egress TCP on port 443 for communication with the Application Migration Service API. + * Egress TCP on port 443 for communication with the MGN API. @@ -75 +75 @@ Ensure that you review the notes below prior to installing the Application Migra - * The VM that hosts the Application Migration Service vCenter Client should only be used for client hosting and should not be used for any other purposes. + * The VM that hosts the MGN vCenter Client should only be used for client hosting and should not be used for any other purposes. @@ -77 +77 @@ Ensure that you review the notes below prior to installing the Application Migra - * Only a trusted administrator should have access to the VM on which the Application Migration Service vCenter Client is installed. + * Only a trusted administrator should have access to the VM on which the MGN vCenter Client is installed. @@ -79 +79 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client should be located in an isolated and dedicated network and considered a sensitive segment. + * The MGN vCenter Client should be located in an isolated and dedicated network and considered a sensitive segment. @@ -88 +88 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client installer only supports vCenter 6.7, 7.0 and 8.0. + * The MGN vCenter Client installer only supports vCenter 6.7, 7.0 and 8.0. @@ -90 +90 @@ Ensure that you review the notes below prior to installing the Application Migra - * The Application Migration Service vCenter Client can be installed on these 64 bit Linux versions: + * The MGN vCenter Client can be installed on these 64 bit Linux versions: @@ -153 +153 @@ Optional arguments: - * AWS Application Migration Service supports VM hardware version 7 and higher with CBT activated. Ensure that you upgrade any VMs you have to hardware version 7 or higher. Ensure that CBT support is activated in your vSphere deployment. Application Migration Service activates CBT on replicating VMs. You can deactivate CBT after cutover. + * AWS Transform MGN supports VM hardware version 7 and higher with CBT activated. Ensure that you upgrade any VMs you have to hardware version 7 or higher. Ensure that CBT support is activated in your vSphere deployment. MGN activates CBT on replicating VMs. You can deactivate CBT after cutover. @@ -155 +155 @@ Optional arguments: - * The VM being replicated into Application Migration Service must not contain any existing VMware snapshots. + * The VM being replicated into MGN must not contain any existing VMware snapshots. @@ -157 +157 @@ Optional arguments: - * Once added to Application Migration Service, snapshot-based replication creates snapshots on the replicated VM, which may result in slower disk performance. + * Once added to MGN, snapshot-based replication creates snapshots on the replicated VM, which may result in slower disk performance. @@ -159 +159 @@ Optional arguments: - * VMs with independent disks, Raw Device Mappings (RDM), or direct-attach disks (iSCSI, NBD) are not supported for replication into Application Migration Service. + * VMs with independent disks, Raw Device Mappings (RDM), or direct-attach disks (iSCSI, NBD) are not supported for replication into MGN. @@ -161 +161 @@ Optional arguments: - * 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. + * The VM being replicated into MGN can be either stopped or running. Changing the VM state during data replication does not affect data replication and causes no data corruption. @@ -174 +174 @@ Generating vCenter Client IAM credentials -Application Migration Service vCenter Client installation instructions +MGN vCenter Client installation instructions