MGN agentless stalled on "authenticate with service"



I'm testing MGN service with agentless method. I've configured the service in an onpremise VM, discovery runs OK, but when I start a replication, I get stalled at "Failed to authenticate with service".

For what I was able to troubleshoot, I think the problem is that the replication server cannot download the agent from the s3 bucket.

I've configured an s3 interface endpoint on my VPC, is there a way to make MGN use it? editing the vcenter-client.config and adding the proper s3 url endpoint?


asked 2 years ago1626 views
3 Answers

A similar problem regarding private endpoints happen with the agent installation:

 [user@host tmp]# python3 --region us-east-2 --aws-access-key-id MY_KEY --aws-secret-access-key MY_SECRET --endpoint MY_MGN_PRIVATE_ENDPOINT_URL --s3-endpoint MY_S3_PRIVATE_ENDPOINT_URL
The installation of the AWS Replication Agent has started.
Downloading of '' from S3 Endpoint MY_S3_PRIVATE_ENDPOINT_URL failed.
This is usually caused by lack of routing to AWS, firewall configuration that block the connection (local or in a firewall appliance) or an incorrect web proxy configuration on this server.
Resolve the connectivity issue and run the installer again.
Learn more about connectivity issues in our documentation at
Error details: <urlopen error [Errno -2] Name or service not known>

But if I try to download the agent manually using the private endpoint, it works ok:

[user@host tmp]# curl https://aws-application-migration-service-us-east-2.MY_S3_PRIVATE_ENDPOINT/latest/linux/aws-replication-installer-64bit -o latest_installer
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19.7M  100 19.7M    0     0  1026k      0  0:00:19  0:00:19 --:--:-- 1136k
[user@host tmp]# ls -l latest_installer 
-rw-r--r--. 1 root root 20665936 Aug 26 13:12 latest_installer

Does anyone know what I'm doing wrong??


answered 2 years ago
  • How did you fix this errors? I have face this similar error when installing Agent. Can you help me please?? Thank you so much


For it to work, I had to switch to a public subnet with public IP enabled for the replication instance to work properly. So, I guess there is something that I misconfigured or MGN doesn't work with private endpoints.

answered 2 years ago

For future reference, I've managed to overcome this issue by hardcoding the DNS in the source server HOSTS file.

Next I would try to create an inbound Route53 endpoint and point my servers resolv.conf to that so that the private endpoints dns entries resolve to the correct IP's inside the private subnet.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions