- Newest
- Most votes
- Most comments
Based on the information provided, it seems you're encountering a specific issue during the replication process with AWS Application Migration Service (AMS) for your Red Hat 8.10 server. The error occurs at the "Connect AWS Replication Agent to Replication Server" step, which is one of the final stages in the initial sync process.
Given that you've already verified the required port connections (1500 and 443) and installed the necessary package (elfutils-libelf-devel), there are a few other potential causes to consider:
-
Network connectivity issues: Even though you've confirmed the ports are open, there might be other network-related problems preventing communication between the agent, replication server, and AWS MGN endpoint.
-
Firewall rules: Ensure that there are no firewall rules on the source server or in the network path that could be blocking the communication.
-
IAM permissions: Verify that the replication server has the proper IAM policy attached to it, allowing it to communicate with the AWS MGN service.
-
DNS issues: In some cases, when using a custom DNS server, DNS traffic may shift to TCP instead of UDP. You might need to update the Migration Service Security Group to allow outbound TCP traffic on port 53.
-
Subnet configuration: Confirm that the replication server is in a subnet with proper access to VPC endpoints for AWS MGN or the public endpoints.
-
Agent version: Ensure you're using the latest version of the AWS Replication Agent.
-
System resources: Check if there are any resource constraints on the source server that might be preventing the agent from functioning correctly.
To troubleshoot further:
-
Review the AWS MGN Agent logs on your Red Hat server for any specific error messages or indications of the problem.
-
Check the CloudTrail logs for any API call errors related to the replication process.
-
Verify that there's sufficient free disk space on both the source server and the replication server.
-
Consider reinstalling the AWS Replication Agent to rule out any installation-related issues.
If the problem persists after checking these potential causes, it would be advisable to contact AWS support for more detailed troubleshooting specific to your environment.
Sources
Common replication errors - Application Migration Service
Troubleshooting communication errors - Application Migration Service
Troubleshooting agent issues - Application Migration Service
Replication related - Application Migration Service
Relevant content
- asked 5 months ago
Thanks Oleksii! Found some errors on agent log:
{"message":"Error creating connection (minor)","log":{"type":"Remote","name":"Agent","level":"WARNING","level_number":30},"source_code":{"line":453,"function":"getChannel","file":"com.amazonaws.cloudendure.agent.driverflavor.ClientCommunicatorDrvFlavor"},"runtime_thread":21,"exception":{"message":"java.net.SocketTimeoutException: connect timed out"
{"message":"RCA_SSL: createOneReplicatorConnection(); cmd:ReplicatorAddress, sourceServerId:s-dd603d8014116bd44, connId:0: 0 ms; new InetSocketAddress(): 1 ms; connectToMachine, replicatorAddress: /(public IP):1500: 0 ms; exception: SocketTimeoutException, msg: [connect timed out]: 10049 ms; end: 0 ms; totalElapsedTime: 10050 ms","log":{"type":"Remote","name":"Agent","level":"INFO","level_number":20},"source_code":{"function":"info","file":"com.amazonaws.cloudendure.common.LogUtils$CELogger"},"runtime_thread":21,"args":[],"origin":{"hostname":"(hostname)"},"@timestamp":"2025-05-20T19:27:53.965Z"}>>> {"message":"Connecting to replicator failed, retrying 5","log":
What about com.amazonaws.cloudendure? There's no mention of this URL on documentation: https://docs.aws.amazon.com/mgn/latest/ug/preparing-environments.html On the other hand, looks like is trying port 1500 on the replication servers' public IP. Updated the replication settings to replicate with private IP but I'm getting the same error: "Connect AWS Replication Agent to Replication Server"