AWS mgn documentation change
Summary
Updated guidance on using AWS Local Zones for staging area subnet, clarifying that MGN doesn't require special configuration but recommends using the parent AWS Region for optimal performance.
Security assessment
The change focuses on performance optimization and configuration flexibility without mentioning security vulnerabilities, weaknesses, or security features.
Diff
diff --git a/mgn/latest/ug/preparing-environments.md b/mgn/latest/ug/preparing-environments.md index adc12f8b2..4840157aa 100644 --- a//mgn/latest/ug/preparing-environments.md +++ b//mgn/latest/ug/preparing-environments.md @@ -64 +64,3 @@ Before setting up MGN you should create a subnet which will be used by the servi -When planning to migrate to an AWS Local Zone, we recommend setting the staging area subnet within the AWS Region, and not the Local Zone. This ensures optimal launch conditions for the replication servers and conversion servers involved in the migration process. However, if you have specific requirements to use the Local Zone for the staging area subnet, we recommend performing thorough testing and validation to ensure you can successfully replicate and cut over your workloads without any issues. +MGN does not require special configuration for AWS Local Zones. You specify a staging area subnet and a launch subnet. MGN uses whichever subnet you provide, regardless of whether it is in an Availability Zone or a Local Zone. + +For optimal performance of replication servers and conversion servers, we recommend placing the staging area subnet in the parent AWS Region rather than the Local Zone. If your requirements dictate using a Local Zone subnet for the staging area, we recommend testing replication and cutover thoroughly before proceeding with production migrations.