I'm encountering issues provisioning with Ansible via SSH from outside our
datacenter (well, AWS Virtual Private Cloud).
Our bastion hosts ("jump boxes") are configured to accept SSH keys from
staff members. Boxes behind the bastion hosts accept only the SSH keys
created for the jumpbox user on the bastion hosts. This makes our
administration easier in the event of key compromise staff turnover (only
need to rotate out on the jumpboxes).
The ProxyCommand examples I've seen for Ansible rely on agent forwarding
and netcat. I want Ansible to SSH in to the bastion host, then run a
second SSH command with the private key of the bastion host. Thus agent
forwarding is useless here. I've tried replacing the netcat ProxyCommand
with "ssh -q -t awsjumpbox1 ssh -p %p %h" and I get mysterious failures
that even -vvvv doesn't provide much insight on. For instance:
fatal: [172.31.17.144] => SSH Error: -bash: line 1:
SSH-2.0-OpenSSH_6.6.1_hpn13v11: command not found
It is sometimes useful to re-run the command using -vvvv, which prints SSH
debug output to help diagnose the issue.
Our ansible.cfg looks like:
host_key_checking = False
ssh_args = -o ControlPersist=15m -F ssh.config -q
scp_if_ssh = True
control_path = ~/.ssh/mux-%%r@%%h:%%p
Our ssh.config (simplified) looks like:
#ProxyCommand ssh -q -A -t jumpbox nc %h %p # have tried
this one too
ProxyCommand ssh -q -t jumpbox ssh -p %p %h
Our boxes are running the standard Amazon AMI (which I am led to believe
are CentOS-based). We are open to rethinking the aforementioned strategy
re: the keys if that's the only way.
I'll be interested in anyone's thoughts on the matter. Thank you.
Senior DevOps Engineer at Edlio Inc
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c5fcf811-fed6-493e-8f4f-1fe818d7824b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.