AWS transform documentation change
Summary
Updated references from 'AWS Application Migration Service' to 'AWS Transform MGN' or 'MGN' throughout the documentation, including links and service names.
Security assessment
The changes involve rebranding/renaming of service references without altering security policies, permissions, or procedures. The principle of least privilege mention remains unchanged. No security vulnerability fixes or new security features are introduced.
Diff
diff --git a/transform/latest/userguide/transform-vmware-connect-target-account.md b/transform/latest/userguide/transform-vmware-connect-target-account.md index d1aeb4214..0f0df4b91 100644 --- a//transform/latest/userguide/transform-vmware-connect-target-account.md +++ b//transform/latest/userguide/transform-vmware-connect-target-account.md @@ -19 +19 @@ Choose whether you are performing a single-account or multi-account migration: - * **Multi-account migration** – Workloads migrate to different target accounts. The connector must be connected to the organization management account or a Delegated Administrator (DA) account registered for both AWS Application Migration Service (Application Migration Service) and CloudFormation StackSets. + * **Multi-account migration** – Workloads migrate to different target accounts. The connector must be connected to the organization management account or a Delegated Administrator (DA) account registered for both AWS Transform MGN and CloudFormation StackSets. @@ -41 +41 @@ When you approve the connector request, you grant AWS Transform permissions to: - * Manage Amazon S3 bucket operations (read/write) for VMware migration, along with access to AWS Migration Hub and AWS Application Migration Service (Application Migration Service). This includes permissions for the following items, all restricted to resources within the target account that are tagged with `CreatedBy:AWSTransform` or `CreatedFor:AWSTransform`: + * Manage Amazon S3 bucket operations (read/write) for VMware migration, along with access to AWS Migration Hub and AWS Application Migration Service (MGN). This includes permissions for the following items, all restricted to resources within the target account that are tagged with `CreatedBy:AWSTransform` or `CreatedFor:AWSTransform`: @@ -82 +82 @@ Connector target account | The account your AWS Transform connector is configure - * **Multi-account migration** – Connect to the organization management account or a Delegated Administrator (DA) account. The DA account must be registered as delegated administrator for both Application Migration Service and CloudFormation StackSets in your AWS Organization. AWS Transform checks whether the connected account is the management account or a DA account and adjusts its behavior accordingly. + * **Multi-account migration** – Connect to the organization management account or a Delegated Administrator (DA) account. The DA account must be registered as delegated administrator for both MGN and CloudFormation StackSets in your AWS Organization. AWS Transform checks whether the connected account is the management account or a DA account and adjusts its behavior accordingly. @@ -89 +89 @@ Target account | The AWS account where your workloads are migrated to. In a sing -For multi-account migrations, AWS recommends that you use a Delegated Administrator (DA) account rather than the organization management account directly. A DA account follows the principle of least privilege by limiting the scope of permissions required for migration operations. The DA account must be registered as delegated administrator for both Application Migration Service and CloudFormation StackSets in your AWS Organization. +For multi-account migrations, AWS recommends that you use a Delegated Administrator (DA) account rather than the organization management account directly. A DA account follows the principle of least privilege by limiting the scope of permissions required for migration operations. The DA account must be registered as delegated administrator for both MGN and CloudFormation StackSets in your AWS Organization. @@ -93 +93 @@ The key difference between the two options is: - * **Management account** – Can enable trusted access for Application Migration Service and CloudFormation StackSets across the organization. AWS Transform calls CloudFormation StackSets APIs with `CallAs: SELF`. + * **Management account** – Can enable trusted access for MGN and CloudFormation StackSets across the organization. AWS Transform calls CloudFormation StackSets APIs with `CallAs: SELF`. @@ -95 +95 @@ The key difference between the two options is: - * **Delegated Administrator account** – Cannot enable trusted access directly (that must be done from the management account), but can manage Application Migration Service source servers, launch instances, and deploy CloudFormation StackSets across member accounts. AWS Transform calls CloudFormation StackSets APIs with `CallAs: DELEGATED_ADMIN`. + * **Delegated Administrator account** – Cannot enable trusted access directly (that must be done from the management account), but can manage MGN source servers, launch instances, and deploy CloudFormation StackSets across member accounts. AWS Transform calls CloudFormation StackSets APIs with `CallAs: DELEGATED_ADMIN`. @@ -100 +100 @@ The key difference between the two options is: -For more information, see [Delegated administrator for Application Migration Service](https://docs.aws.amazon.com/mgn/latest/ug/mgn-delegated-admin.html) in the _Application Migration Service User Guide_. +For more information, see [Delegated administrator for MGN](https://docs.aws.amazon.com/mgn/latest/ug/mgn-delegated-admin.html) in the _MGN User Guide_. @@ -157 +157 @@ AWS Transform uses the `kms:DescribeKey` permission to verify the key exists, an -If you plan to modify the AWS Application Migration Service template to enable post-launch actions, add the following permission to the target connector role. This JSON policy statement grants the `iam:PassRole` permission for the post-launch actions role. You can find the role name in the **Collaboration** tab after the connector is created. For information about adding permissions to a role, see [Update permissions for a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_update-role-permissions.html) in the _IAM User Guide_. +If you plan to modify the AWS Transform MGN template to enable post-launch actions, add the following permission to the target connector role. This JSON policy statement grants the `iam:PassRole` permission for the post-launch actions role. You can find the role name in the **Collaboration** tab after the connector is created. For information about adding permissions to a role, see [Update permissions for a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_update-role-permissions.html) in the _IAM User Guide_.