ansible-playbook provision_jenkins.yaml

PLAY [Configure Jenkins Server] ************************************************************************************************************************************************************

TASK [Gathering Facts] *********************************************************************************************************************************************************************
fatal: [ubuntu@ec2-18-206-165-43.compute-1.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host ec2-18-206-165-43.compute-1.amazonaws.com port 22: Connection timed out", "unreachable": true}

PLAY RECAP *********************************************************************************************************************************************************************************
ubuntu@ec2-18-206-165-43.compute-1.amazonaws.com : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

Группа хостов для дженкинса как называется у вас в инвентаре?

[webservers]

ubuntu@ec2-54-227-64-53.compute-1.amazonaws.com ansible_ssh_private_key_file=~/Downloads/zeyjam.pem

[jenkins]

ubuntu@ec2-18-206-165-43.compute-1.amazonaws.com ansible_ssh_private_key_file=~/Downloads/zeyjam.pem

[webservers]

ubuntu@ec2-54-227-64-53.compute-1.amazonaws.com ansible_ssh_private_key_file=~/Downloads/zeyjam.pem

[jenkins]

ubuntu@ec2-18-206-165-43.compute-1.amazonaws.com ansible_ssh_private_key_file=~/Downloads/zeyjam.pem

Добавьте ansible_ssh_timeout: 120

я новичек. извиняюсь я так понял в инвентарь добавить?

Ключи вообще лучше через ssh-agent подкидывать. Самый надежный способ

You can define different become options for each managed node or group. You can define these variables in inventory or use them as normal variables.