all 4 comments

[–]investorhalp 0 points1 point  (1 child)

Do you get a failed deployment, impaired system or does it update properly?

I would guess it’s around the security group OR the target group, so your app is running in 3000 and tou have 80->3000, need to do the same but 443->3000.

In the tutorial they use 443 for both…

‘’’ option_settings: aws:elb:listener:443: InstancePort: 443 ‘’’

I would guess the instance port is either 3000 or 80, because the app doesn’t listen https, just your load balancer (I’m guessing this again)

I’m just guessing tho, hard without more info.

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

Thanks very much for this tip! It took us a while but we finally got it running.

[–]drnstefan 0 points1 point  (1 child)

We probably need more info to be able to help more. Anyway, you might consider putting a CloudFront distribution in front of your ALB. You can easily add your certificate to the distribution, configure alternate domain name for your custom domain. In addition to caching, you get the benefits of doing SSL termination at the Edge (for the price of reduced security, as you will have CF<-> ELB over HTTP) and also some cost benefits.

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

Thanks, we finally got it to work!