1 Answer
- Newest
- Most votes
- Most comments
0
This is likely caused by a permissions issue from MGN service to launch the Replication Instance. Noting, that the problem here is in launching the server that receives the data from your on-prem server, and not an issue with your on-prem server.
Try checking the logs, usually it'll say if there is a IAM Role or permission missing.
answered 2 years ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago