# SSL termination for docker-compose deploy

**URL:** <https://forum.ansible.com/t/ssl-termination-for-docker-compose-deploy/29217>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [December 7, 2018, 4:30pm UTC](https://forum.ansible.com/t/ssl-termination-for-docker-compose-deploy/29217 "2018-12-07T16:30:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmakovey](https://avatars.discourse-cdn.com/v4/letter/d/4da419/32.png) [@dmakovey](https://forum.ansible.com/u/dmakovey)\
**Post date:** [December 7, 2018, 4:30pm UTC](https://forum.ansible.com/t/ssl-termination-for-docker-compose-deploy/29217/1 "2018-12-07T16:30:04Z")

</div>

Hi,

I've found open issue on SSL termination for AWX:  
[https://github.com/ansible/awx/issues/1549](https://github.com/ansible/awx/issues/1549) however there seems to be no  
traction on it.

It is hard for me to believe community is running AWX over HTTP (vs  
HTTPS). So the question is: how do people run \*theirs\* AWX with SSL? Is  
everybody spinning up additional LB/proxies to handle SSL termination,  
or hack built-in nginx?

---

<div class="post-metadata">

**Author:** ![Sujith\_A\_R1](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@Sujith\_A\_R1](https://forum.ansible.com/u/Sujith_A_R1)\
**Post date:** [December 7, 2018, 4:33pm UTC](https://forum.ansible.com/t/ssl-termination-for-docker-compose-deploy/29217/2 "2018-12-07T16:33:05Z")

</div>

Bring that simple . Add in compose file to spin up a nginx container with SSL termination to awx\_web port 8052.

---

<div class="post-metadata">

**Author:** ![dmakovey](https://avatars.discourse-cdn.com/v4/letter/d/4da419/32.png) [@dmakovey](https://forum.ansible.com/u/dmakovey)\
**Post date:** [December 7, 2018, 4:49pm UTC](https://forum.ansible.com/t/ssl-termination-for-docker-compose-deploy/29217/3 "2018-12-07T16:49:53Z")

</div>

> Bring that simple . Add in compose file to spin up a nginx container  
> with SSL termination to awx\_web port 8052.

so that would be using "external" nginx to terminate SSL. I get that.  
That is the most obvious option, but that's an extra entity to maintain,  
not to mention that awx's nginx is still hanging out on public port 80.

thus I was curious about [re]configuring internal nginx, or perhaps  
missing some obvious step in documentation someplace.

IS it the concensus that one needs to implement external SSL termination  
and \*not\* use existing infrastructure?
