You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using your playbook. it creates ec2 instances but not able to ssh into them, I have disabled assign public ip on this subnets. I dont want to have public ip address, is it good idea to create jumpbox and then use ansible from that jumpbox?
fatal: [] => SSH Error: Permission denied (publickey,keyboard-interactive).
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
The text was updated successfully, but these errors were encountered:
Hi,
I think you have to verify credentials, certificates, access that are managed by AWS from your console panel.
Since you have your own configuration my placeholder-config may not fit your needs.
I think that Ansible is creating the machine on AWS but then some misconfiguration does not allow it to SSH into the instance. Double check from AWS EC2 Console.
Eventually re-run the playbook, sometimes it is not idempotential and when failing, launching it again against an already existing instance may succeed
Hi Sergio,
I am using your playbook. it creates ec2 instances but not able to ssh into them, I have disabled assign public ip on this subnets. I dont want to have public ip address, is it good idea to create jumpbox and then use ansible from that jumpbox?
fatal: [] => SSH Error: Permission denied (publickey,keyboard-interactive).
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
The text was updated successfully, but these errors were encountered: