# Spin Up Jenkins on AWS instance

**URL:** <https://forum.ansible.com/t/spin-up-jenkins-on-aws-instance/22505>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [September 7, 2016, 11:57am UTC](https://forum.ansible.com/t/spin-up-jenkins-on-aws-instance/22505 "2016-09-07T11:57:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Liora\_Milbaum](https://avatars.discourse-cdn.com/v4/letter/l/838e76/32.png) [@Liora\_Milbaum](https://forum.ansible.com/u/Liora_Milbaum)\
**Post date:** [September 7, 2016, 11:57am UTC](https://forum.ansible.com/t/spin-up-jenkins-on-aws-instance/22505/1 "2016-09-07T11:57:26Z")

</div>

I can provision the ec2 instance but the setup task fails with the message:

fatal: [54.166.83.128]: UNREACHABLE! =\> {“changed”: false, “msg”: “Failed to connect to the host via ssh.”, “unreachable”: true}

Any idea how to fix/troubleshoot this issue?

I am newbie to Ansible.

Thanks,  
Liora

---

<div class="post-metadata">

**Author:** ![rup](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@rup](https://forum.ansible.com/u/rup)\
**Post date:** [September 8, 2016, 5:25pm UTC](https://forum.ansible.com/t/spin-up-jenkins-on-aws-instance/22505/2 "2016-09-08T17:25:42Z")

</div>

Sometimes it’s a matter of timing. If it’s sporadically happening, perhaps the ssh connection isn’t happening within the 10 second default used by Ansible. To override this default you need to specify in your config file.