Thanks for all the work on Docker for AWS, awesome.
Just wondering how I might configure Docker for AWS to terminate https traffic in an ELB listener created via a ‘service create’ command and allow http to pass through to our app service containers running in the swarm?
I’ve tried a few things including:
adding a new https 443 to http 80 listener manually on the ELB created by Docker for AWS, it was promptly removed though I presume by CloudFormation/Docker. While it was created, both port 80 and 443 wouldn’t accept any requests and hung.
published port 443 (external) to port 3000 (container ie. our app port), this created a ELB mapping 443 to 443 but with a tcp/tcp layer - I tried changing it to https/http and it kind of worked, curling it gave me the certificate details in a http trace, but loading the actual page contents timed out.
published port 80 to port 3000 and changed the port 80 listener from tcp to https, but similar results as above. First request went through (not all assets on the page loaded), and subsequent requests timed out.
Any recommendations for how I should be handling https traffic with the ELBs in Docker for AWS?