AWS mgn documentation change
Summary
Rebranding of 'Application Migration Service' to 'AWS Transform MGN' throughout the documentation, including security group references and service terminology updates.
Security assessment
Changes are purely cosmetic rebranding updates without modifications to security mechanisms, protocols, or configurations. All security-related content (EBS encryption, security groups, KMS permissions) remains functionally identical, only with updated service names. No vulnerabilities or weaknesses are addressed.
Diff
diff --git a/mgn/latest/ug/replication-server-settings.md b/mgn/latest/ug/replication-server-settings.md index f16fbcc6c..b31f32368 100644 --- a//mgn/latest/ug/replication-server-settings.md +++ b//mgn/latest/ug/replication-server-settings.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 @@ -Staging area subnetReplication server instance typeDedicated instance for replication serverAmazon EBS volume typeAmazon EBS encryptionStore snapshots in AWS Local ZoneAlways use Application Migration Service security groupData routing and throttlingReplication resources tags +Staging area subnetReplication server instance typeDedicated instance for replication serverAmazon EBS volume typeAmazon EBS encryptionStore snapshots in AWS Local ZoneAlways use AWS Transform MGN security groupData routing and throttlingReplication resources tags @@ -13 +13 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -Replication servers are lightweight Amazon EC2 instances that are used to replicate data between your source servers and AWS. Replication servers are automatically launched and terminated as needed. You can modify the behavior of the replication servers by modifying the settings for a single source server or multiple source servers. Alternatively, you can run AWS Application Migration Service with the default replication server settings. +Replication servers are lightweight Amazon EC2 instances that are used to replicate data between your source servers and AWS. Replication servers are automatically launched and terminated as needed. You can modify the behavior of the replication servers by modifying the settings for a single source server or multiple source servers. Alternatively, you can run AWS Transform MGN with the default replication server settings. @@ -60 +60 @@ Choose the **Replication server instance type**. This determines the instance ty -The best practice is to not change the default replication server instance type unless there is a business need for doing so. By default, AWS Application Migration Service uses the **t3.small** instance type. This is the most cost effective instance type and should work well for most common workloads. You can change the replication server instance type to speed up the initial sync of data from your source servers to AWS. Changing the instance type will likely lead to increased compute costs. +The best practice is to not change the default replication server instance type unless there is a business need for doing so. By default, AWS Transform MGN uses the **t3.small** instance type. This is the most cost effective instance type and should work well for most common workloads. You can change the replication server instance type to speed up the initial sync of data from your source servers to AWS. Changing the instance type will likely lead to increased compute costs. @@ -140 +140 @@ You can customize the Amazon EBS volume type used by each disk within each sourc -For information about Amazon EBS volume limits, see [What are the Amazon EBS volume limits for AWS Application Migration Service?](./AWS-Related-FAQ.html#ebs-limits-faq) +For information about Amazon EBS volume limits, see [What are the Amazon EBS volume limits for AWS Transform MGN?](./AWS-Related-FAQ.html#ebs-limits-faq) @@ -165 +165 @@ Reversing the encryption option after data replication has started will cause da -If you decide to use a Customer Managed Key (CMK), or if your default Amazon EBS encryption key is a CMK, you will need to add additional permissions to the key to allow AWS Application Migration Service to use it. +If you decide to use a Customer Managed Key (CMK), or if your default Amazon EBS encryption key is a CMK, you will need to add additional permissions to the key to allow AWS Transform MGN to use it. @@ -169 +169 @@ To modify the existing key policy using the AWS Management Console _policy view_ - 1. Navigate to the AWS KMS Console and select the AWS KMS key you plan to use with Application Migration Service. + 1. Navigate to the AWS KMS Console and select the AWS KMS key you plan to use with MGN. @@ -197 +197 @@ To modify the existing key policy using the AWS Management Console _policy view_ - "Sid": "Allow AWS MGN permissions to use a customer managed key for EBS encryption", + "Sid": "Allow MGN permissions to use a customer managed key for EBS encryption", @@ -231 +231 @@ To modify the existing key policy using the AWS Management Console _policy view_ - "Sid": "Allow EC2 to use this key on behalf of the current AWS MGN user, during target launches", + "Sid": "Allow EC2 to use this key on behalf of the current MGN user, during target launches", @@ -299 +299 @@ For more information about local snapshots in Local Zones, see [Local snapshots -## Always use Application Migration Service security group +## Always use AWS Transform MGN security group @@ -301 +301 @@ For more information about local snapshots in Local Zones, see [Local snapshots -Choose whether you would like to **Always use the Application Migration Service security group**. +Choose whether you would like to **Always use the AWS Transform MGN security group**. @@ -305 +305 @@ A security group acts as a virtual firewall, which controls the inbound and outb -The best practice is to have AWS Application Migration Service automatically attach and monitor the default Application Migration Service Security Group. This group opens inbound TCP Port 1500 for receiving the transferred replicated data. When the default Application Migration Service Security Group is activated, Application Migration Service will constantly monitor whether the rules within this security group are enforced, in order to maintain uninterrupted data replication. If these rules are altered, Application Migration Service will automatically fix the issue. +The best practice is to have AWS Transform MGN automatically attach and monitor the default AWS Transform MGN Security Group. This group opens inbound TCP Port 1500 for receiving the transferred replicated data. When the default AWS Transform MGN Security Group is activated, MGN will constantly monitor whether the rules within this security group are enforced, in order to maintain uninterrupted data replication. If these rules are altered, MGN will automatically fix the issue. @@ -307 +307 @@ The best practice is to have AWS Application Migration Service automatically att -Select the **Always use Application Migration Service security group** option to allow data to flow from your source servers to the replication servers, and that the replication servers can communicate their state to the AWS Application Migration Service servers. +Select the **Always use AWS Transform MGN security group** option to allow data to flow from your source servers to the replication servers, and that the replication servers can communicate their state to the AWS Transform MGN servers. @@ -315 +315 @@ You can search for a specific security group within the search box. -You can add security groups via the AWS Management Console, and they will appear on the security group drop-down list in the AWS Application Migration Service Console. Learn more about AWS security groups in [this VPC article](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html). +You can add security groups via the AWS Management Console, and they will appear on the security group drop-down list in the AWS Transform MGN Console. Learn more about AWS security groups in [this VPC article](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html). @@ -317 +317 @@ You can add security groups via the AWS Management Console, and they will appear -You can use the default Application Migration Service security group, or you can select another security group. However, take into consideration that any selected security group that is not the Application Migration Service default, will be added to the default group, since the default security group is essential for the operation of Application Migration Service. +You can use the default AWS Transform MGN security group, or you can select another security group. However, take into consideration that any selected security group that is not the AWS Transform MGN default, will be added to the default group, since the default security group is essential for the operation of MGN. @@ -321 +321 @@ You can use the default Application Migration Service security group, or you can -AWS Application Migration Service allows you to control how data is routed from your source servers to the replication servers on AWS through the **Data routing and throttling** settings. +AWS Transform MGN allows you to control how data is routed from your source servers to the replication servers on AWS through the **Data routing and throttling** settings. @@ -367 +367 @@ The following diagram illustrates the high-level interaction between the differe - + @@ -375 +375 @@ When the **Use private IP** option is chosen, you will have the option to create -You can control the amount of network bandwidth used for data replication per server. By default, AWS Application Migration Service will use all available network bandwidth utilizing five concurrent connections. +You can control the amount of network bandwidth used for data replication per server. By default, AWS Transform MGN will use all available network bandwidth utilizing five concurrent connections. @@ -383 +383 @@ If you chose to throttle bandwidth, the **Throttle network bandwidth** (per serv -Add custom **Replication resources tags** to resources created by AWS Application Migration Service in your AWS account. +Add custom **Replication resources tags** to resources created by AWS Transform MGN in your AWS account. @@ -385 +385 @@ Add custom **Replication resources tags** to resources created by AWS Applicatio -These are resources required to facilitate data replication, testing and cutover. Each tag consists of a key and an optional value. You can add a custom tag to all of the AWS resources that are created on your AWS account during the normal operation of AWS Application Migration Service. +These are resources required to facilitate data replication, testing and cutover. Each tag consists of a key and an optional value. You can add a custom tag to all of the AWS resources that are created on your AWS account during the normal operation of AWS Transform MGN. @@ -398 +398 @@ To add a new tag, take the following steps: -Application Migration Service already adds tags to every resource it creates, including service tags and user tags. +MGN already adds tags to every resource it creates, including service tags and user tags.