News for hackers. Stuff that matters.

A comment on Why Puppet Should Manage Your Infrastructure. Parent comment

Re:Why Puppet Should Manage Your Infrastructure by jollojou on Tuesday March 08, 2011 @09:27AM (#2300912)
That's correct. The problem is that the EC2 internal IPs change even though the instance would have an Elastic IP. EC2 instances use internal IPs when communicating with other EC2 instances (this is a feature of AWS DNS). As a consequence, Puppet clients cannot access the master by using the master's Elastic IP.
[ Parent | on HN ]
Re:Why Puppet Should Manage Your Infrastructure by legooolas on Tuesday March 08, 2011 @09:41AM (#2300963)
That sounds rather inconvenient. Are the external elastic IPs non-routable internally? I mean, if you add the IPs explicitly to hosts files then will traffic to those IPs not work?
[ Parent | on HN ]