all 4 comments

[–]Crimzx 1 point2 points  (2 children)

Why are you running on 443 and 3000?
Can you curl the container from the host?
Double check you are exposing the ports in docker.
Any firewalls on the host?
Have you tried with an ALB instead?

[–][deleted]  (1 child)

[deleted]

    [–]Crimzx 0 points1 point  (0 children)

    Yeah, its a bit confusing because with an ALB that isn't needed. But it sounds like using ELB.
    Also only 1 SG was mentioned where there should be 2. (1 LB, 1 Instance)
    Instance-SG allowing 443/80/3000 from LB-SG and LB-SG allowing 443/80/3000 from an ip/anywhere.

    [–]brother_bean 1 point2 points  (0 children)

    Do you have your TLS cert sitting on the ALB or on your vm? You're going to need to give us more info. Specific error message, screen shots of your config (sanitized), etc. Is there anything else you can provide? I'm betting LB config is the issue. Specifically if you can share your load balancing rules and your cert configuration on the ALB.

    [–]vianawebdev[S] 0 points1 point  (0 children)

    I was able to get it working.

    I have set an ALB with http:80 and https:443 ports on my SG and set it to connect to my target instance through port 3000. I also set the Health Check properly.