AWS prescriptive-guidance documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in private connectivity context
Security assessment
Consistency update without altering security controls or migration approach.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/conclusion.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/conclusion.md index 821421a50..686b824c2 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/conclusion.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/conclusion.md @@ -7 +7 @@ -This guide covered requirements and provided an example configuration for using Application Migration Service for lift-and-shift migration of servers from secured on-premises networks to AWS over private connectivity (AWS VPN or AWS Direct Connect). This is a typical scenario for many corporate migrations. The guide also provided guidance on ways to test by using automated or manual deployment, and monitoring and troubleshooting connectivity issues if they arise. +This guide covered requirements and provided an example configuration for using Application Migration Service for lift-and-shift migration of servers from secured on-premises networks to AWS over private connectivity (AWS VPN or Direct Connect). This is a typical scenario for many corporate migrations. The guide also provided guidance on ways to test by using automated or manual deployment, and monitoring and troubleshooting connectivity issues if they arise.