search

sw360cab / ansible-slb-tomcat

An ansible playbook to deploy on Amazon AWS a scalable set of instances of Apache Tomcat 7 container proxied via a “load-balancing purpose” instance driven by HAProxy
Apache License 2.0
4 stars 3 forks source link

ansible accessing private ip address #1

Open svennela opened 9 years ago

svennela commented 9 years ago

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.

sw360cab commented 9 years ago

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