1 Answer
- Newest
- Most votes
- Most comments
1
The browser will not see the certificate if your accessing the EC2 via a application oad balancer.
I would ensure you secure your security group on your EC2 and only allow the ALB access.
I suspect your still accessing the webpage directly to the EC2
Relevant content
- asked 3 months ago
- Accepted Answerasked 10 months ago
- asked a year ago
- asked 7 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 days ago
I think you are right. I spent more time on the Route 53 side and found that by checking "Alias" I could enter the id of the load balancer into my "A" records. I think that is the main thing that eventually solved it. The online instructions from AWS were pretty weak in that regard. Thanks for helping me focus in the right direction. I was also able to remove the self signed certificate and found the comment to disable the SSL from that misguided approach. I wish I had ready the full instructions in the certificate creation instructions before starting. Who would want a certificate that still throws an error in browsers trying to connect via SSL? Thank you.