AWS prescriptive-guidance documentation change
Summary
Updated service name from 'AWS Application Migration Service' to 'AWS Transform MGN' throughout the document. All console links, documentation references, and service mentions were updated to reflect the new naming convention.
Security assessment
The changes are purely branding updates (service renaming) without modifications to security-related content. The SELinux security context and security policy requirements remain unchanged. No vulnerabilities or security procedures were altered.
Diff
diff --git a/prescriptive-guidance/latest/patterns/restart-the-aws-replication-agent-automatically-without-disabling-selinux-after-rebooting-a-rhel-source-server.md b/prescriptive-guidance/latest/patterns/restart-the-aws-replication-agent-automatically-without-disabling-selinux-after-rebooting-a-rhel-source-server.md index 30e5edb64..b84e17de0 100644 --- a//prescriptive-guidance/latest/patterns/restart-the-aws-replication-agent-automatically-without-disabling-selinux-after-rebooting-a-rhel-source-server.md +++ b//prescriptive-guidance/latest/patterns/restart-the-aws-replication-agent-automatically-without-disabling-selinux-after-rebooting-a-rhel-source-server.md @@ -15 +15 @@ SummaryPrerequisites and limitationsArchitectureToolsEpicsRelated resources -AWS Application Migration Service helps simplify, expedite, and automate the migration of Red Hat Enterprise Linux (RHEL) workloads to the Amazon Web Services (AWS) Cloud. To add source servers to Application Migration Service, you install the [AWS Replication Agent](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation.html) on the servers. +AWS Transform MGN helps simplify, expedite, and automate the migration of Red Hat Enterprise Linux (RHEL) workloads to the Amazon Web Services (AWS) Cloud. To add source servers to MGN, you install the [AWS Replication Agent](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation.html) on the servers. @@ -17 +17 @@ AWS Application Migration Service helps simplify, expedite, and automate the mig -Application Migration Service provides real-time, asynchronous, block-level replication. This means that you can continue normal IT operations during the entire replication process. These IT operations might require that you reboot or restart your RHEL source server during the migration. If this happens, the AWS Replication Agent will not restart automatically, and your data replication will stop. Typically, you can set Security-Enhanced Linux (SELinux) to **disabled** or **permissive** mode to automatically restart the AWS Replication Agent. However, your organization’s security policies might prohibit disabling SELinux, and you might also have to [relabel your files](https://access.redhat.com/solutions/3176). +MGN provides real-time, asynchronous, block-level replication. This means that you can continue normal IT operations during the entire replication process. These IT operations might require that you reboot or restart your RHEL source server during the migration. If this happens, the AWS Replication Agent will not restart automatically, and your data replication will stop. Typically, you can set Security-Enhanced Linux (SELinux) to **disabled** or **permissive** mode to automatically restart the AWS Replication Agent. However, your organization’s security policies might prohibit disabling SELinux, and you might also have to [relabel your files](https://access.redhat.com/solutions/3176). @@ -29 +29 @@ This pattern describes how to automatically restart the AWS Replication Agent wi - * Application Migration Service initialized from the Application Migration Service console. Initialization is required only the first time you use this service. For instructions, see the [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/mandatory-setup.html). + * MGN initialized from the MGN console. Initialization is required only the first time you use this service. For instructions, see the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/mandatory-setup.html). @@ -31 +31 @@ This pattern describes how to automatically restart the AWS Replication Agent wi - * An existing [AWS Identity and Access Management (IAM) policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) for Application Migration Service. For more information, see the [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/mgn-policies.html). + * An existing [AWS Identity and Access Management (IAM) policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) for MGN. For more information, see the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/mgn-policies.html). @@ -53 +53 @@ The following image shows the architecture for this approach. - * [AWS Application Migration Service](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) is a highly automated lift-and-shift (rehost) solution that simplifies, expedites, and reduces the cost of migrating applications to AWS. + * [AWS Transform MGN](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) is a highly automated lift-and-shift (rehost) solution that simplifies, expedites, and reduces the cost of migrating applications to AWS. @@ -79 +79 @@ Task| Description| Skills required -Generate AWS temporary credentials.| The [temporary credentials](https://docs.aws.amazon.com/mgn/latest/ug/credentials.html) provided by Application Migration Service use a similar mechanism to the one used by [AWS Identity and Access Management Roles Anywhere](https://docs.aws.amazon.com/rolesanywhere/latest/userguide/introduction.html).To create temporary credentials, you need to: +Generate AWS temporary credentials.| The [temporary credentials](https://docs.aws.amazon.com/mgn/latest/ug/credentials.html) provided by MGN use a similar mechanism to the one used by [AWS Identity and Access Management Roles Anywhere](https://docs.aws.amazon.com/rolesanywhere/latest/userguide/introduction.html).To create temporary credentials, you need to: @@ -87,4 +87,4 @@ Install the AWS Replication Agent.| - 1. Sign in to the AWS Management Console and open the [AWS Application Migration Service console](https://console.aws.amazon.com/mgn/home). - 2. Configure replication settings by following the instructions in the [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/template-vs-server.html). - 3. Install the AWS Replication Agent by following the instructions in the [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation-instructions.html). - 4. On the **Source Servers** page, choose the RHEL source server, and then choose **Replication** to start the initial replication. For more information, see the [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/interracting.html). + 1. Sign in to the AWS Management Console and open the [AWS Transform MGN console](https://console.aws.amazon.com/mgn/home). + 2. Configure replication settings by following the instructions in the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/template-vs-server.html). + 3. Install the AWS Replication Agent by following the instructions in the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/agent-installation-instructions.html). + 4. On the **Source Servers** page, choose the RHEL source server, and then choose **Replication** to start the initial replication. For more information, see the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/interracting.html). @@ -111 +111 @@ Check whether the module has been loaded.| Run the following command:`#semodule -Reboot or restart the RHEL source server and verify the data replication status.| Open the AWS Application Migration Service console, navigate to **Data replication progress** , and then reboot or restart your RHEL source server. Data replication should now resume automatically after the RHEL source server reboots.| Migration engineer +Reboot or restart the RHEL source server and verify the data replication status.| Open the AWS Transform MGN console, navigate to **Data replication progress** , and then reboot or restart your RHEL source server. Data replication should now resume automatically after the RHEL source server reboots.| Migration engineer @@ -115 +115 @@ Reboot or restart the RHEL source server and verify the data replication status. - * [Application Migration Service documentation](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) + * [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/what-is-application-migration-service.html) @@ -117 +117 @@ Reboot or restart the RHEL source server and verify the data replication status. - * [Application Migration Service policies](https://docs.aws.amazon.com/mgn/latest/ug/mgn-policies.html) + * [MGN policies](https://docs.aws.amazon.com/mgn/latest/ug/mgn-policies.html)