AWS transform documentation change
Summary
Renamed 'AWS Application Migration Service' to 'AWS Transform MGN (MGN)' throughout the document and updated all related links and terminology
Security assessment
Changes are purely branding/terminology updates with no security vulnerability fixes, security enhancements, or security feature additions mentioned. Updates include service name changes and documentation link adjustments without altering security-related content like permissions, encryption, or access controls.
Diff
diff --git a/transform/latest/userguide/transform-vmware-migrate-servers.md b/transform/latest/userguide/transform-vmware-migrate-servers.md index 6d82a3549..37cc1aff4 100644 --- a//transform/latest/userguide/transform-vmware-migrate-servers.md +++ b//transform/latest/userguide/transform-vmware-migrate-servers.md @@ -11 +11 @@ Prerequisites and migration execution defaultsStep 1: Set up migration waveStep -AWS Transform uses AWS Application Migration Service (Application Migration Service) to rehost your VMware servers to Amazon EC2. The migrate servers workflow guides you through setting up each migration wave, validating your server inventory, deploying replication agents, monitoring data replication, testing migrated instances, and performing final cutover. To read more about it, see [What is AWS Application Migration Service?](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) in the _Application Migration Service User Guide_. +AWS Transform uses AWS Transform MGN (MGN) to rehost your VMware servers to Amazon EC2. The migrate servers workflow guides you through setting up each migration wave, validating your server inventory, deploying replication agents, monitoring data replication, testing migrated instances, and performing final cutover. To read more about it, see [What is AWS Transform MGN?](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) in the _MGN User Guide_. @@ -69 +69 @@ You can modify the suggested Amazon EC2 instance types to include recommendation -To change default launch settings, go to the Application Migration Service console and apply the changes you want. For more information, see [Launch settings](https://docs.aws.amazon.com/mgn/latest/ug/launch-settings.html) in the _Application Migration Service User Guide_. +To change default launch settings, go to the MGN console and apply the changes you want. For more information, see [Launch settings](https://docs.aws.amazon.com/mgn/latest/ug/launch-settings.html) in the _MGN User Guide_. @@ -86 +86 @@ AWS Transform supports two migration modes: -AWS Transform confirms the target account configuration and verifies that Application Migration Service is initialized in each target account. If Application Migration Service is not yet initialized, AWS Transform provides instructions to complete the initialization. During initialization, Application Migration Service creates the following IAM service roles for replication and launch operations: +AWS Transform confirms the target account configuration and verifies that MGN is initialized in each target account. If MGN is not yet initialized, AWS Transform provides instructions to complete the initialization. During initialization, MGN creates the following IAM service roles for replication and launch operations: @@ -103 +103 @@ AWS Transform confirms the target account configuration and verifies that Applic -To learn more about these roles, see [Initializing Application Migration Service with the console](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize-console.html) or [Initializing Application Migration Service with the API](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize-api.html) in the _Application Migration Service User Guide_. +To learn more about these roles, see [Initializing MGN with the console](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize-console.html) or [Initializing MGN with the API](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize-api.html) in the _MGN User Guide_. @@ -137 +137 @@ AWS Transform adds networking information from your network migration to the inv -To change replication and launch settings, go to the Application Migration Service console and apply the changes you want. For more information, see [Replication settings](https://docs.aws.amazon.com/mgn/latest/ug/replication-settings.html) and [Launch settings](https://docs.aws.amazon.com/mgn/latest/ug/launch-settings.html) in the _Application Migration Service User Guide_. +To change replication and launch settings, go to the MGN console and apply the changes you want. For more information, see [Replication settings](https://docs.aws.amazon.com/mgn/latest/ug/replication-settings.html) and [Launch settings](https://docs.aws.amazon.com/mgn/latest/ug/launch-settings.html) in the _MGN User Guide_. @@ -156 +156 @@ If you selected the MAP security groups mapping strategy during network migratio -Before loading your server data into Application Migration Service, AWS Transform prepares the inventory file for your review. You can download the file in CSV or XLSX format, review the server configurations, and make changes if needed. +Before loading your server data into MGN, AWS Transform prepares the inventory file for your review. You can download the file in CSV or XLSX format, review the server configurations, and make changes if needed. @@ -175 +175 @@ You can modify the file to adjust Amazon EC2 configurations, change operating sy -After you review the inventory, you can either accept it as shown or upload a modified version. AWS Transform then loads the data into Application Migration Service, which creates source server records for each server in the wave. +After you review the inventory, you can either accept it as shown or upload a modified version. AWS Transform then loads the data into MGN, which creates source server records for each server in the wave. @@ -185 +185 @@ AWS Transform allows one import to a given target AWS account and target AWS Reg -You can control the operating system licensing options (BYOL or License Included) and tenancy by specifying the configuration in the inventory file columns `mgn:launch:placement:operating-system-licensing` and `mgn:launch:placement:tenancy`. For more information, see [Import parameters](https://docs.aws.amazon.com/mgn/latest/ug/import-main.html#import-parameters) in the _Application Migration Service User Guide_. +You can control the operating system licensing options (BYOL or License Included) and tenancy by specifying the configuration in the inventory file columns `mgn:launch:placement:operating-system-licensing` and `mgn:launch:placement:tenancy`. For more information, see [Import parameters](https://docs.aws.amazon.com/mgn/latest/ug/import-main.html#import-parameters) in the _MGN User Guide_. @@ -193 +193 @@ To begin replicating data from your source servers to AWS, you install the AWS R - * **MGN connector** – Use an Application Migration Service connector to automate agent installation. The connector connects to source machines over SSH (Linux) or WinRM (Windows) and installs the replication agent automatically. Once configured, a connector can be reused across multiple waves and different target AWS accounts. For more information about the Application Migration Service connector, see [Set up the MGN Connector](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-setup-instructions.html) in the _Application Migration Service User Guide_. + * **MGN connector** – Use an MGN connector to automate agent installation. The connector connects to source machines over SSH (Linux) or WinRM (Windows) and installs the replication agent automatically. Once configured, a connector can be reused across multiple waves and different target AWS accounts. For more information about the MGN connector, see [Set up the MGN Connector](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-setup-instructions.html) in the _MGN User Guide_. @@ -235 +235 @@ Requirement | Details -Operating system | Supported Linux operating system. For the full list, see [MGN connector prerequisites](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-prerequisites.html) in the _Application Migration Service User Guide_. +Operating system | Supported Linux operating system. For the full list, see [MGN connector prerequisites](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-prerequisites.html) in the _MGN User Guide_. @@ -237 +237 @@ Network access | Must reach all source servers (Linux over SSH, Windows over Win -Internet connectivity | Outbound HTTPS (443) to AWS endpoints (Systems Manager, Secrets Manager, Application Migration Service) +Internet connectivity | Outbound HTTPS (443) to AWS endpoints (Systems Manager, Secrets Manager, MGN) @@ -251 +251 @@ AWS Transform guides you through the following steps to set up the connector: -Provide a name for your connector, or use the auto-generated default name. The connector can be installed on the management account or on a delegated administrator account in Application Migration Service. For multi-account migrations, the connector can deploy agents to servers across member accounts. +Provide a name for your connector, or use the auto-generated default name. The connector can be installed on the management account or on a delegated administrator account in MGN. For multi-account migrations, the connector can deploy agents to servers across member accounts. @@ -295 +295 @@ Install the connector on a Linux machine in your environment: -After installation, AWS Transform identifies all source servers that belong to the current wave and automatically attaches them to the Application Migration Service connector. +After installation, AWS Transform identifies all source servers that belong to the current wave and automatically attaches them to the MGN connector. @@ -314 +314 @@ You can combine the Linux and Windows single-secret options if you have both ser -Credential secret format. To read more about it, see [MGN connector credentials](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-credentials.html) in the _Application Migration Service User Guide_ : +Credential secret format. To read more about it, see [MGN connector credentials](https://docs.aws.amazon.com/mgn/latest/ug/mgn-connector-credentials.html) in the _MGN User Guide_ : @@ -368 +368 @@ For manual installation, you first generate AWS credentials (temporary or perman - * **Temporary credentials (recommended)** – Create an IAM role with the `AWSApplicationMigrationAgentInstallationPolicy` managed policy, then use `aws sts assume-role` to generate temporary credentials. To read more about it, see [Agent installation permissions](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation-permissions.html) in the _Application Migration Service User Guide_. + * **Temporary credentials (recommended)** – Create an IAM role with the `AWSApplicationMigrationAgentInstallationPolicy` managed policy, then use `aws sts assume-role` to generate temporary credentials. To read more about it, see [Agent installation permissions](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation-permissions.html) in the _MGN User Guide_. @@ -394 +394 @@ For Windows servers, download and run the appropriate installer using PowerShell -The `--user-provided-id` parameter is required. Replace `server-identifier` with the exact value from the `mgn:server:user-provided-id` column in your inventory file. This identifier links the physical server to its Application Migration Service source server record. +The `--user-provided-id` parameter is required. Replace `server-identifier` with the exact value from the `mgn:server:user-provided-id` column in your inventory file. This identifier links the physical server to its MGN source server record. @@ -396 +396 @@ The `--user-provided-id` parameter is required. Replace `server-identifier` with -For more information about agent installation, see [Linux agent](https://docs.aws.amazon.com/mgn/latest/ug/linux-agent.html) and [Windows agent](https://docs.aws.amazon.com/mgn/latest/ug/windows-agent.html) in the _Application Migration Service User Guide_. +For more information about agent installation, see [Linux agent](https://docs.aws.amazon.com/mgn/latest/ug/linux-agent.html) and [Windows agent](https://docs.aws.amazon.com/mgn/latest/ug/windows-agent.html) in the _MGN User Guide_. @@ -402 +402 @@ After installation, AWS Transform verifies that all agents are successfully conn -AWS Transform does not support Application Migration Service agentless replication. For information about agentless replication, see [Agentless replication overview](https://docs.aws.amazon.com/mgn/latest/ug/installing-vcenter-overview-mgn.html) in the _Application Migration Service User Guide_. +AWS Transform does not support MGN agentless replication. For information about agentless replication, see [Agentless replication overview](https://docs.aws.amazon.com/mgn/latest/ug/installing-vcenter-overview-mgn.html) in the _MGN User Guide_. @@ -408 +408 @@ You must install the replication agent on all servers in a wave. Disconnect and -For quotas related to replication, see [Application Migration Service service quota limits](https://docs.aws.amazon.com/mgn/latest/ug/MGN-service-limits.html) in the _Application Migration Service User Guide_. +For quotas related to replication, see [MGN service quota limits](https://docs.aws.amazon.com/mgn/latest/ug/MGN-service-limits.html) in the _MGN User Guide_. @@ -423 +423 @@ The replication process consists of two phases: -Replication servers are temporary Amazon EC2 instances deployed in the staging area subnet. They receive replicated data from source servers and are automatically managed by Application Migration Service. To read more about it, see [Replication server settings](https://docs.aws.amazon.com/mgn/latest/ug/replication-server-settings.html) in the _Application Migration Service User Guide_. +Replication servers are temporary Amazon EC2 instances deployed in the staging area subnet. They receive replicated data from source servers and are automatically managed by MGN. To read more about it, see [Replication server settings](https://docs.aws.amazon.com/mgn/latest/ug/replication-server-settings.html) in the _MGN User Guide_. @@ -451 +451 @@ You can control replication for individual servers or the entire wave at any tim -After data replication is complete, you can launch test instances to validate your migrated servers before performing the final cutover. To read more about it, see [Launch test instances](https://docs.aws.amazon.com/mgn/latest/ug/launch-test-instances.html) in the _Application Migration Service User Guide_. AWS Transform supports two testing options: +After data replication is complete, you can launch test instances to validate your migrated servers before performing the final cutover. To read more about it, see [Launch test instances](https://docs.aws.amazon.com/mgn/latest/ug/launch-test-instances.html) in the _MGN User Guide_. AWS Transform supports two testing options: @@ -477 +477 @@ After testing is complete and you are satisfied with the results, mark your appl -Cutover is the final migration step where your production workloads are moved to AWS. To read more about it, see [Launch cutover instances](https://docs.aws.amazon.com/mgn/latest/ug/launch-cutover-instances.html) in the _Application Migration Service User Guide_. Similar to testing, AWS Transform supports full wave cutover or selective cutover for specific servers. +Cutover is the final migration step where your production workloads are moved to AWS. To read more about it, see [Launch cutover instances](https://docs.aws.amazon.com/mgn/latest/ug/launch-cutover-instances.html) in the _MGN User Guide_. Similar to testing, AWS Transform supports full wave cutover or selective cutover for specific servers. @@ -487 +487 @@ The cutover process includes the following steps: - 3. **Finalize cutover** – Confirm the cutover to stop source machine replication. You can finalize all servers in the wave or select specific servers. Finalization stops replication agents from sending data, removes replication agents from source servers, and locks the server lifecycle state. This action cannot be easily undone. To read more about it, see [Finalize cutover](https://docs.aws.amazon.com/mgn/latest/ug/finalize-cutover.html) in the _Application Migration Service User Guide_. + 3. **Finalize cutover** – Confirm the cutover to stop source machine replication. You can finalize all servers in the wave or select specific servers. Finalization stops replication agents from sending data, removes replication agents from source servers, and locks the server lifecycle state. This action cannot be easily undone. To read more about it, see [Finalize cutover](https://docs.aws.amazon.com/mgn/latest/ug/finalize-cutover.html) in the _MGN User Guide_. @@ -504 +504 @@ Downtime occurs between source shutdown and cutover instance availability. Plan -During migration, each server progresses through the following lifecycle states. To read more about it, see [Source server lifecycle](https://docs.aws.amazon.com/mgn/latest/ug/source-server-lifecycle.html) in the _Application Migration Service User Guide_. +During migration, each server progresses through the following lifecycle states. To read more about it, see [Source server lifecycle](https://docs.aws.amazon.com/mgn/latest/ug/source-server-lifecycle.html) in the _MGN User Guide_. @@ -518 +518 @@ During migration, each server progresses through the following lifecycle states. - * **Disconnected** – The server has been disconnected from Application Migration Service. + * **Disconnected** – The server has been disconnected from MGN.