AWS/EC2 ambari installation error 'Connection failed to http://ip-172-31-18-1.ca-central-1.comp...'

[#1]

All my nodes and services have this same error --Connection failed to http://ip-172-31-18-1.ca-central-1.comp...'.

I believe I setup passwdless correctly(I done it many times and all worked before), my security group to setup all TCP, all UDP and SSH. do any one think this is AWS/EC2/DNS problem? since all connection fails, no exception. any idea?

thank you so much for your help.

[#2]

@Robin Dong

Sometimes this can happen in a scenario where as soon as the instances are shutdown and restarted back, the IP addresses and hostnames change, which means the cluster doesn’t know where to find its various services.

.

[#3]

Thank you so much for this quick respond. why are IP and hostname changed?

my network.hostname=localhost, no change on /etc/sysconfig/network file. did I missed anything?

is this AWS/EC2 networking DNS problem? I already created a ticket to AWS support. do you think I can fix it on my side.

[#4 · Accepted solution]

@Robin Dong

If your instance is in a VPC and you assign it an Elastic IP address, it receives an IPv4 DNS hostname if DNS hostnames are enabled. For more information, see Using DNS with Your VPC in the Amazon VPC User Guide. [1] & [2]

Note: Instances that access other instances through their public NAT IP address are charged for regional or Internet data transfer, depending on whether the instances are in the same region.

[1] Reference Doc: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html

[2] http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html

AWS Forums (reporting such behaviour): https://forums.aws.amazon.com/thread.jspa?threadID=122633

.

[#5]

you are right, Since my setting all working before I never use VCP and just thought about this is may be a cause. I will work on it and get back to you. thanks again.