Complete SSL on load balancing platform before elastic bean stack

Question

Okay, so I'm very close to having the Amazon SSL I generated complete on ALB, which is placed in front of my web application that runs on Elastic Beanstalk.

What I have done so far is to add the alb-secure-listener.config file to the .ebextensions folder in the root of my application directory, the contents of this file are as follows:

option_settings:
    aws:elbv2:listener:443:
        DefaultProcess: https
        ListenerEnabled: 'true'
        Protocol: HTTPS
        SSLCertificateArns: arn:aws:acm:us-east-1:#############:certificate/####################################
    aws:elasticbeanstalk:environment:process:https:
        Port: '443'
        Protocol: HTTPS

If the string with all ### is replaced by my SSL ARN.

Now, when I open https://mywebapp.com , I get the “502 Bad Gateway” page instead of my webapp, this page - however - has an SSL certificate that I want to use.

Opening http://mywebapp.com displays the site as usual.

, - , , , , , : D

Answer 1

ALB EC2 HTTP 80. :

Port: '80'
Protocol: HTTP