Thank you for your reply. I am definitely going to watch your talk, that’s precisely the kind of topic I would like to understand better.
I haven’t got any load balancer at the moment. I had one before as described in my answer to @cnck1387 and try know to make it work without it. I wanted at first to use an Application Load Balancer, but as my registrar does not provide ALIAS records and that it is not possible to use an Elastic IP to point to an ALB, I had to use a Network Load Balancer instead. From what I read on the AWS blog, Network Load Balancers offer TLS termination since January 2019. I am a bit unfamiliar with all these concepts, does this mean that everything behind this load balancer doesn’t need to run on HTTPS? This is contradicting some other posts I have read saying that everything behind a Network Load Balancer should be on HTTPS, but those posts might have been written before TLS termination was possible with this type of load balancers.
Regarding the port mapping, I see in my task definition that my port 80 is mapped to the port 4000, and the port 443 is mapped to port 5000, which is what I expect it to be. The volumes mapped are correct too. Everything seems good there. These values in the task are created automatically from my docker-compose file with ecs-cli compose in my deployment script, so I do not expect big surprises in there.
I will try to turn the logging on to see if I can get more info. Thanks for the suggestion.
For the load balancer, I really want to try to make it work without it first. Or at least understand why it is impossibe if this is the case.
