2 Answers
- Newest
- Most votes
- Most comments
1
Check the replication subnet to see if the replication server exists. If it does it's probably a communication issue between the replication server and MGN. Check routing, NACLs, and Security Group. https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html
If there's not a replication server, its creation might be blocked by Service Control Policies or Control Tower Guard Rails (For instance, I've seen tagging requirements block the creation of the replication server). Check Cloud Trail and Cloud Watch for hints.
answered 3 years ago
1
Check your settings under the Application Migration Service in your region. Verify that the subnet in the settings is the expected one.
Relevant content
- asked 9 months ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
yes some policy were stopping its resolved now but now new error has came out i.e. Failed to connect AWS Replication Agent to Replication Server.