search

rundeck-plugins / rundeck-ec2-nodes-plugin

Get resource node data from Amazon EC2
85 stars 45 forks source link

Not connecting non-public IP nodes #17

Closed edcorfa closed 8 years ago

edcorfa commented 10 years ago

I can run jobs in nodes that have a public IP address, but not to the internal ones.

Checking on the "Nodes" section, I can see that the user is set as "ec2-user" but the hostname field is empty.

Is there a way to force the connection threw internal IP?

gschueler commented 10 years ago

you will have to change the mapping from ec2 instance data to use the private IP for the hostname. Try changing the hostname.selector to something like this:

hostname.selector=publicDnsName,privateDnsName,privateIpAddress

This should set hostname to the public dns name, otherwise the private dns/ip if public is not available. Or you can take out the publicDnsName

stack72 commented 9 years ago

I have tested this specific mapping and it works :)

dvg06 commented 7 years ago

When I add this, I get 2 host name fields - one with private dns and other one is blank. Apparently rundeck is trying to use the blank one, and I end up with below errors. any help please?

Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-01addfae' 16:10:05 i-0e638cdf Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-0e638cdf' 16:10:05 i-2335778c Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-2335778c' 16:10:05 i-27ce8e88 Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-27ce8e88'