Can't connect to HTTPS on ec2 after setting up Load Balancer

by Chris   Last Updated September 11, 2019 10:00 AM

  1. I have an EC2 instance with Amazon Linux running an Apache web server.

  2. I have an ACM SSL certificate issued. (I want to use it for a sub domain so I have set it up using *.mydomain.com and it has been issued)

  3. I have setup an applicaiton load balancer with listners on port 80 and 443 open. I have attached the SSL Certificate to it.

  4. I have setup my target group that contains my EC2 instance. I have setup forwarding on port 80 as per AWS documentation.

As far as I undertand, the only thing left for me to do is to point my domain which is hosted through GoDaddy at my Load Balancer. I found a tutorial that said to create an A record set to Alias and add the DNS Namefor my Load Balancer as the value. When I do this, it tells me that I cannot have the A record because I have already got one setup but that is for my sub domain. I am doing this through Route 53.

When I give the A record a different name; for example, lb.test.example.com it does not connect to HTTP on the domain test.example.com. When I type in lb.test.example.com, I get the browser winging that the site is not secure and then a Bad Gateway error.

What am I missing here?



Related Questions


Https configuration on AWS

Updated June 24, 2018 15:00 PM

Apache where to add rewrite rule

Updated June 26, 2017 15:00 PM

HTTPS works only with Load Balancer DNS - AWS

Updated June 16, 2019 02:00 AM