# AWX through bastion/jump hosts

**URL:** <https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [October 2, 2017, 11:11pm UTC](https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667 "2017-10-02T23:11:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Weald](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@Simon\_Weald](https://forum.ansible.com/u/Simon_Weald)\
**Post date:** [October 2, 2017, 11:11pm UTC](https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667/1 "2017-10-02T23:11:13Z")

</div>

I’m looking to manage some nodes which are in a separate subnet behind a jump host. Previously I set up a few SSH config options for my Ansible user and then configured the jump host to respect these (keys, user, ports etc) - doing the same with AWX seems a little out of my reach at the moment. On the IRC channel it was suggested that I could do the same in /var/lib/awx in the awx\_task container, so I did this, but to no avail.

I can see AWX attempting to connect in auth.log on the jump host:

`Connection closed by 78.x.x.x port 33062 [preauth]`

And the full output from AWX is here (suitable sanitised):

[https://gist.github.com/analbeard/a950f1e577468a28c02eeb4dbd27338f](https://gist.github.com/analbeard/a950f1e577468a28c02eeb4dbd27338f)

Obviously manually adding config files to a container isn’t a maintainable way of doing this in future, but I’d like to get it working so I can experiment more. Can anyone suggest where I might be going wrong?

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [October 3, 2017, 12:19am UTC](https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667/2 "2017-10-03T00:19:46Z")

</div>

In this case it looks like I might have given you some incorrect information. Currently in the standalone docker container we run as the root user. I’m going to be changing this in the near future to execute as the awx user (which is our intention)… so for the moment it looks like root is who you’ll need to be. Can you try putting that configuration under that user instead? We’ll see if we can come up with a more tenable solution in the future.

---

<div class="post-metadata">

**Author:** ![Simon\_Weald](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@Simon\_Weald](https://forum.ansible.com/u/Simon_Weald)\
**Post date:** [October 3, 2017, 8:59am UTC](https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667/3 "2017-10-03T08:59:59Z")

</div>

Not a problem Matt, all input/help is much appreciated!

I have now got this working with your revised advise above - would you like me to open an issue?

Thanks!

---

<div class="post-metadata">

**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\
**Post date:** [October 3, 2017, 11:47am UTC](https://forum.ansible.com/t/awx-through-bastion-jump-hosts/25667/4 "2017-10-03T11:47:58Z")

</div>

I know it’s weird and probably doesn’t seem like it, but this will be the issue where this gets fixed: [https://github.com/ansible/awx/issues/89](https://github.com/ansible/awx/issues/89)