AWS prescriptive-guidance documentation change
Summary
Updated all references from 'Application Migration Service' to 'MGN' or 'AWS Transform MGN' throughout the document, including migration patterns, tool metadata, and attribute descriptions.
Security assessment
The changes are purely a rebranding of the service name without any modifications to security-related content or functionality. Security attributes like 'replication_server_security_group' remain unchanged in purpose and description, only now associated with MGN instead of Application Migration Service.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-portfolio-playbook/metadata.md b/prescriptive-guidance/latest/large-migration-portfolio-playbook/metadata.md index 25622f716..90936748c 100644 --- a//prescriptive-guidance/latest/large-migration-portfolio-playbook/metadata.md +++ b//prescriptive-guidance/latest/large-migration-portfolio-playbook/metadata.md @@ -70 +70 @@ _Supporting tasks_ include the operational activities that the portfolio and mig - * AWS Application Migration Service + * AWS Transform MGN @@ -98 +98 @@ The following are examples: - * Rehost (action) waves, applications, or servers (source object) to Amazon EC2 (target object) using Application Migration Service or Cloud Migration Factory (tools) + * Rehost (action) waves, applications, or servers (source object) to Amazon EC2 (target object) using MGN or Cloud Migration Factory (tools) @@ -113 +113 @@ The following are examples: -The following is an example of how you might record _Pattern 1: Rehost to Amazon EC2 using Application Migration Service or Cloud Migration Factory_ from the [migration patterns table](./discovery.html#migration-patterns). +The following is an example of how you might record _Pattern 1: Rehost to Amazon EC2 using MGN or Cloud Migration Factory_ from the [migration patterns table](./discovery.html#migration-patterns). @@ -117 +117 @@ The following is an example of how you might record _Pattern 1: Rehost to Amazon -**Pattern name** | Rehost to Amazon EC2 using Application Migration Service or Cloud Migration Factory +**Pattern name** | Rehost to Amazon EC2 using MGN or Cloud Migration Factory @@ -120 +120 @@ The following is an example of how you might record _Pattern 1: Rehost to Amazon -**Tools** | Application Migration Service or Cloud Migration Factory +**Tools** | MGN or Cloud Migration Factory @@ -125 +125 @@ The following is an example of how you might record _Pattern 1: Rehost to Amazon -Now that you have defined the pattern or task, you determine the metadata required for the source object, target object, tools, and other business information. To explain this process, this playbook uses _Pattern 1: Rehost to Amazon EC2 using Application Migration Service or Cloud Migration Factory_ from the [migration patterns table](./discovery.html#migration-patterns) as an example. Note that for some patterns or tasks, some steps might not apply. +Now that you have defined the pattern or task, you determine the metadata required for the source object, target object, tools, and other business information. To explain this process, this playbook uses _Pattern 1: Rehost to Amazon EC2 using MGN or Cloud Migration Factory_ from the [migration patterns table](./discovery.html#migration-patterns) as an example. Note that for some patterns or tasks, some steps might not apply. @@ -142 +142 @@ Attribute name | Object type | Description or purpose - 2. **Analyze the tools** – Use the tool to create a target object and check for differences. Capture the tool-specific metadata as demonstrated in the following table, and remove the attributes from the previous table if it is not supported by the migration tool. For example, you cannot customize the OS type and storage size for Application Migration Service because the rehost migration tool is like-for-like. Therefore, you would remove target OS and target disk size if these attributes were included in the previous table. In the previous example table, all attributes are supported by the tool, so no action is required. + 2. **Analyze the tools** – Use the tool to create a target object and check for differences. Capture the tool-specific metadata as demonstrated in the following table, and remove the attributes from the previous table if it is not supported by the migration tool. For example, you cannot customize the OS type and storage size for MGN because the rehost migration tool is like-for-like. Therefore, you would remove target OS and target disk size if these attributes were included in the previous table. In the previous example table, all attributes are supported by the tool, so no action is required. @@ -148,4 +148,4 @@ Attribute name | Object type | Description or purpose -`AWS_account_ID` | Tools (Application Migration Service) | AWS account ID for AWS Application Migration Service -`AWS_Region` | Tools (Application Migration Service) | AWS Region for Application Migration Service -`replication_server_subnet` | Tools (Application Migration Service) | Subnet for the Application Migration Service replication server -`replication_server_security_group` | Tools (Application Migration Service) | Security group for the Application Migration Service replication server +`AWS_account_ID` | Tools (MGN) | AWS account ID for AWS Transform MGN +`AWS_Region` | Tools (MGN) | AWS Region for MGN +`replication_server_subnet` | Tools (MGN) | Subnet for the MGN replication server +`replication_server_security_group` | Tools (MGN) | Security group for the MGN replication server @@ -185 +185 @@ Attribute name | Object type | Description or purpose - 4. **Consider other attributes** – In addition to the primary action, consider other actions and attributes related to the target object or application. For the example pattern, _Pattern 1: Rehost to Amazon EC2 using Application Migration Service or Cloud Migration Factory_ , the action is rehost, and the target object is Amazon EC2. Other related actions for this target object might include backing up to Amazon EC2, monitoring the EC2 instance after the migration, and using tags to manage costs associated with the EC2 instance. You might also want to consider other application attributes that help you manage the migration, such as the application owner, who you might need to contact for questions or cutover purposes. + 4. **Consider other attributes** – In addition to the primary action, consider other actions and attributes related to the target object or application. For the example pattern, _Pattern 1: Rehost to Amazon EC2 using MGN or Cloud Migration Factory_ , the action is rehost, and the target object is Amazon EC2. Other related actions for this target object might include backing up to Amazon EC2, monitoring the EC2 instance after the migration, and using tags to manage costs associated with the EC2 instance. You might also want to consider other application attributes that help you manage the migration, such as the application owner, who you might need to contact for questions or cutover purposes. @@ -208,4 +208,4 @@ Attribute name | Object type | Description or purpose -`AWS_account_ID` | Tools (Application Migration Service) | AWS account to host the target EC2 instance -`AWS_Region` | Tools (Application Migration Service) | AWS Region to host the target EC2 instance -`replication_server_subnet` | Tools (Application Migration Service) | Subnet for the Application Migration Service replication server -`replication_server_security_group` | Tools (Application Migration Service) | Security group for the Application Migration Service replication server +`AWS_account_ID` | Tools (MGN) | AWS account to host the target EC2 instance +`AWS_Region` | Tools (MGN) | AWS Region to host the target EC2 instance +`replication_server_subnet` | Tools (MGN) | Subnet for the MGN replication server +`replication_server_security_group` | Tools (MGN) | Security group for the MGN replication server @@ -291,2 +291,2 @@ Metadata attribute | Metadata type | Metadata sources -`replication_server_subnet` | Tools (Application Migration Service) | Landing zone design documentation -`replication_server_security_group` | Tools (Application Migration Service) | Landing zone design documentation +`replication_server_subnet` | Tools (MGN) | Landing zone design documentation +`replication_server_security_group` | Tools (MGN) | Landing zone design documentation