When creating a slave node under a different AWS account in the same region, Jenkins is unable to ssh into the slave. The logs of the slaves just shows it continuously trying to ssh in but it times out. I can see from the AWS UI the slave is correctly created and started. I am able to ssh into it from my terminal. I don't know if this is possible yet but it should be noted somewhere and not allowed to start the slave if this sort of functionality isn't available yet.