AWS mgn documentation change
Summary
Renamed 'Application Migration Service' to 'MGN' or 'AWS Transform MGN' throughout the documentation. Updated section headers, descriptions, and terminology to reflect the new service branding.
Security assessment
The changes are purely branding/naming updates without modifications to security protocols, configurations, or vulnerabilities. Existing security statements about TLS encryption, port requirements, and firewall configurations remain unchanged except for service name replacements. No evidence of security vulnerability fixes or new security guidance.
Diff
diff --git a/mgn/latest/ug/preparing-environments.md b/mgn/latest/ug/preparing-environments.md index 3ebee4375..e7e7830e4 100644 --- a//mgn/latest/ug/preparing-environments.md +++ b//mgn/latest/ug/preparing-environments.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) @@ -11 +11 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -# Network requirements for Application Migration Service +# Network requirements for MGN @@ -13 +13 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -Before you use Application Migration Service, make sure to prepare your environments. Preparation includes setting correct network settings, defining network requirements, and opening the correct ports. +Before you use MGN, make sure to prepare your environments. Preparation includes setting correct network settings, defining network requirements, and opening the correct ports. @@ -30 +30 @@ Before you use Application Migration Service, make sure to prepare your environm -Watch the [AWS Application Migration Service - Service architecture and network architecture video](https://youtu.be/ao8geVzmmRo) for an in-depth overview of the Application Migration Service architecture. +Watch the [AWS Transform MGN - Service architecture and network architecture video](https://youtu.be/ao8geVzmmRo) for an in-depth overview of the MGN architecture. @@ -32 +32 @@ Watch the [AWS Application Migration Service - Service architecture and network -This is the Application Migration Service network diagram: +This is the MGN network diagram: @@ -34 +34 @@ This is the Application Migration Service network diagram: - + @@ -53 +53 @@ As part of network setting preparations, set up a staging area and operational s -Before setting up Application Migration Service you should create a subnet which will be used by the service as a staging area for data replicated from your source servers to AWS. +Before setting up MGN you should create a subnet which will be used by the service as a staging area for data replicated from your source servers to AWS. @@ -68 +68 @@ When planning to migrate to an AWS Local Zone, we recommend setting the staging -Test and cutover instances are launched in a subnet you specify in the Amazon EC2 launch template associated with each source server. The Amazon EC2 launch template is created automatically when you add a source server to AWS Application Migration Service. +Test and cutover instances are launched in a subnet you specify in the Amazon EC2 launch template associated with each source server. The Amazon EC2 launch template is created automatically when you add a source server to AWS Transform MGN. @@ -76 +76 @@ Test and cutover instances are launched in a subnet you specify in the Amazon EC -If your source servers are domain-joined to an Active Directory, ensure that the target VPC has network connectivity and DNS resolution to your AD domain controllers before launching test or cutover instances. During conversion, Application Migration Service resets network settings to use DHCP, which means instance-level DNS overrides from the source server are not preserved. +If your source servers are domain-joined to an Active Directory, ensure that the target VPC has network connectivity and DNS resolution to your AD domain controllers before launching test or cutover instances. During conversion, MGN resets network settings to use DHCP, which means instance-level DNS overrides from the source server are not preserved. @@ -82 +82 @@ For details on configuring DNS and network connectivity for domain-joined server -To prepare your network for running AWS Application Migration Service, configure the following connectivity settings. All communication is encrypted with TLS. +To prepare your network for running AWS Transform MGN, configure the following connectivity settings. All communication is encrypted with TLS. @@ -86 +86 @@ To prepare your network for running AWS Application Migration Service, configure -SSL interception should not be applied for communication between replication servers and the Application Migration Service API endpoint, or between source servers and the Application Migration Service API endpoint. +SSL interception should not be applied for communication between replication servers and the MGN API endpoint, or between source servers and the MGN API endpoint. @@ -92 +92 @@ SSL interception should not be applied for communication between replication ser - * Communication between source servers and AWS Application Migration Service over TCP port 443 + * Communication between source servers and AWS Transform MGN over TCP port 443 @@ -96 +96 @@ SSL interception should not be applied for communication between replication ser - * Communication between the staging area subnet and AWS Application Migration Service over TCP port 443 + * Communication between the staging area subnet and AWS Transform MGN over TCP port 443 @@ -107 +107 @@ Add the following endpoints and URLs to your firewall allowlist. -**Application Migration Service API endpoints** +**MGN API endpoints** @@ -181 +181 @@ JSON -### Communication between source servers and AWS Application Migration Service over TCP port 443 +### Communication between source servers and AWS Transform MGN over TCP port 443 @@ -183 +183 @@ JSON -Each source server that is added to Application Migration Service must continuously communicate with the Application Migration Service API endpoint over TCP port 443. +Each source server that is added to MGN must continuously communicate with the MGN API endpoint over TCP port 443. @@ -189 +189 @@ The main operations performed through this route are: - * Connecting the source servers to the Application Migration Service console and displaying their replication status. + * Connecting the source servers to the MGN console and displaying their replication status. @@ -195 +195 @@ The main operations performed through this route are: - * Transmitting source server information to the Application Migration Service console (hardware information, running services, installed applications and packages). + * Transmitting source server information to the MGN console (hardware information, running services, installed applications and packages). @@ -208 +208 @@ The replicated data is encrypted and compressed when transferred over TCP port 1 -AWS Application Migration Service uses TLS 1.2 end to end from the agent installed on the source server to the Replication Server. Each replication server gets assigned a specific TLS server certificate, which is distributed to the corresponding Agent and validated on the agent side. +AWS Transform MGN uses TLS 1.2 end to end from the agent installed on the source server to the Replication Server. Each replication server gets assigned a specific TLS server certificate, which is distributed to the corresponding Agent and validated on the agent side. @@ -210 +210 @@ AWS Application Migration Service uses TLS 1.2 end to end from the agent install -### Communication between the staging area subnet and AWS Application Migration Service over TCP port 443 +### Communication between the staging area subnet and AWS Transform MGN over TCP port 443 @@ -212 +212 @@ AWS Application Migration Service uses TLS 1.2 end to end from the agent install -The replication servers in the staging area subnet must continuously communicate with Application Migration Service over TCP port 443. The main operations performed through this route are: +The replication servers in the staging area subnet must continuously communicate with MGN over TCP port 443. The main operations performed through this route are: @@ -216 +216 @@ The replication servers in the staging area subnet must continuously communicate - * Connecting the replication servers to Application Migration Service and displaying their replication status. + * Connecting the replication servers to MGN and displaying their replication status. @@ -264 +264 @@ Without access to the AL2023 package repository, replication servers may fail to -If there is no connection between your source servers and Application Migration Service, make sure that your corporate firewall enables connectivity from the source servers to Application Migration Service over TCP port 443. If the connectivity is blocked, enable it. +If there is no connection between your source servers and MGN, make sure that your corporate firewall enables connectivity from the source servers to MGN over TCP port 443. If the connectivity is blocked, enable it.