Elastic IPs not handled correctly #196

temujin9 opened this Issue Oct 18, 2012 · 4 comments


None yet

4 participants


They don't automatically attach, or factor into attempts to SSH into a host they're attached to.


I have a similar issue that a private IP address (assigned as part of a VPC) isn't being used for SSH attempts. These instances don't have public IPs or hostnames that surface for connectivity.

schade commented Nov 2, 2012

Are the two types of Elastic IP been treated as one? They seem to be different animals.

From the 'normal' Elastic IP Docs...

If you're using Amazon Virtual Private Cloud: There's a separate pool of Elastic IP addresses to use with Amazon VPC. Your Amazon EC2 Elastic IP addresses won't work with instances in a VPC, and your VPC Elastic IP addresses won't work with instances in EC2. The following sections describe how to work with EC2 addresses, which have different characteristics than VPC Elastic IP addresses...

Therein could lie the problem if we're expecting them to be similar.

temujin9 commented Nov 2, 2012

@schade - Deliverables are:

  • Code in lib/ironfan/providers/ec2 to attach a specified Elastic IP (which is hand-generated) to a machine on launch.
  • Code in lib/chef/knife/cluster_ssh.rb or other appropriate place to make knife cluster ssh work with the IP
  • Testing done to ensure that this code works both in and out of VPC environments
schade commented Nov 20, 2012

Part 1) attaching a specified Elastic IP in cluster definition now associates properly; however,
Part 2) connecting via ElasticIP via 'knife cluster ssh ' is not yet complete.

Current code can be viewed at my fork schade/ironfan@e6418e6.
I will setup a pull request once the functionality of part 2 is complete.

Note: the changes to lib/ironfan/dsl/ec2.rb are merely removal of some of my testing code. All actual changes were done outside of the dsl.

No primates were harmed in the generation of this code...

@schade schade referenced this issue Dec 10, 2012

196_elastic_ips #219

@temujin9 temujin9 closed this Dec 11, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment