AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-07-10 · Documentation low

File: prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/monitoring.md

Summary

Updated terminology and formatting: changed 'AWS Sessions Manager' to 'AWS Systems Manager Session Manager', standardized 'MGN' references, removed code formatting from 'cmd', and corrected 'EC2 instance' to 'Amazon EC2 instance'.

Security assessment

Changes involve terminology corrections and formatting adjustments without introducing security content. The update to 'AWS Systems Manager Session Manager' improves accuracy but doesn't address vulnerabilities or add security guidance.

Diff

diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/monitoring.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/monitoring.md
index 41ad519f5..42aa14dad 100644
--- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/monitoring.md
+++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/monitoring.md
@@ -5 +5 @@
-[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating on-premises servers to AWS over private networks by using AWS Transform MGN](welcome.html)
+[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating on-premises servers to AWS over private networks by using AWS Transform MGN](introduction.html)
@@ -11 +11 @@ Testing connectivity and name resolution from the source serverTesting connectiv
-You can monitor MGN by using [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/), [Amazon EventBridge](https://aws.amazon.com/eventbridge), and [AWS CloudTrail](https://aws.amazon.com/cloudtrail/), which collect raw data and process it into readable, near-real-time metrics. For more information, see [Monitoring Application Migration Service](https://docs.aws.amazon.com/mgn/latest/ug/monitoring-overview.html) in the AWS documentation. 
+You can monitor AWS Transform MGN by using [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/), [Amazon EventBridge](https://aws.amazon.com/eventbridge), and [AWS CloudTrail](https://aws.amazon.com/cloudtrail/), which collect raw data and process it into readable, near-real-time metrics. For more information, see [Monitoring AWS Transform MGN](https://docs.aws.amazon.com/mgn/latest/ug/monitoring-overview.html) in the AWS documentation. 
@@ -15 +15 @@ If you encounter any issues and want to launch new test or cutover instances, yo
-When the Agent has been installed, the source server appears on the Application Migration Service console, and you can see the server details to check replication progress. 
+When the Agent has been installed, the source server appears on the MGN console, and you can see the server details to check replication progress. 
@@ -19 +19 @@ When the Agent has been installed, the source server appears on the Application
-Log in to the source server by using Windows remote desktop protocol (RDP), Secure Shell (SSH), or AWS Sessions Manager, and test the following:
+Log in to the source server by using Windows remote desktop protocol (RDP), Secure Shell (SSH), or AWS Systems Manager Session Manager, and test the following:
@@ -27 +27 @@ Log in to the source server by using Windows remote desktop protocol (RDP), Secu
-    * On Linux or Windows (`cmd`):
+    * On Linux or Windows (cmd):
@@ -37 +37 @@ Log in to the source server by using Windows remote desktop protocol (RDP), Secu
-    * On Linux or Windows (`cmd`):
+    * On Linux or Windows (cmd):
@@ -47 +47 @@ Log in to the source server by using Windows remote desktop protocol (RDP), Secu
-    * On Linux or Windows (`cmd`):
+    * On Linux or Windows (cmd):
@@ -65 +65 @@ In addition, make sure that the Amazon EC2 and MGN API endpoints resolve to priv
-To test connectivity from the staging area, launch a temporarily EC2 instance in the staging subnet and test the following: 
+To test connectivity from the staging area, launch a temporarily Amazon EC2 instance in the staging subnet and test the following: 
@@ -73 +73 @@ To test connectivity from the staging area, launch a temporarily EC2 instance in
-    * On Linux or Windows (`cmd`):
+    * On Linux or Windows (cmd):
@@ -83 +83 @@ To test connectivity from the staging area, launch a temporarily EC2 instance in
-    * On Linux or Windows (`cmd`):
+    * On Linux or Windows (cmd):