title: Jenkins EC2 slave SSH failure
body: <p>Using the Jenkins EC2 plugin, I cannot get my Jenkins master to SSH to my Jenkins slave. The slave spins up and provisions properly, but:</p>
  
  <p><code>INFO: Connecting to 10.99.3.6 on port 22, with timeout 10000.
  Feb 24, 2016 5:13:27 PM hudson.plugins.ec2.EC2Cloud log
  INFO: Failed to connect via ssh: There was a problem while connecting to 10.99.3.6:22</code></p>
  
  <p>Though the Jenkins host claims to be failing when attempting to ssh to the slave node, I am able to ssh from a shell on the Jenkins host without error, and using the same authentication keys as specified in my configuration.</p>
  
  <p>I have additionally attempted to add and <code>id_rsa</code> file containing the same key inputted in the EC2 configuration in a <code>.ssh</code> directory in the Jenkins home dir, and the <code>ec2-user</code> home dir, which also did not work (which wasn't entirely unexpected).</p>
  
  <p>Jenkins - v1.649</p>
  
  <p>Amazon EC2 Plugin - v1.31</p>
  
  <p>Using in-house Centos7.1 AMIs</p>
  
  <p>Additional information:  The slave instance ID is listed in the build executor box, but says "offline" next to it, even after I observe the instance in the EC2 console as running and available, and am able to SSH to it manually from the master.</p>