amazon web services - AWS Elastic Load Balancer flags environment as Red because TLS enabled on EC instance
We are using AWS Elastic Beanstalk with Application type Load Balancer to deploy a .NET applications.
In the beginning we had a wildcard cert that we used on the load balancer level. The actual EC instance and the IIS on there did not handle TLS traffic since the load balancer stripped connection down to non-TLS. Everything was fine. However, later we needed to install an SSO (service provider) tool on the instance and this tool requires TLS. We ended up, in addition to the cert on the load balancer creating a Lets Encrypt cert on the EC instance level.
What ended up happening after this, is AWS keeps flagging all our instances as having health of Red because load balancer keeps trying to request http://localhost:443 (or http://IP:443) and these are not coming back.
I tried using a self signed cert bound to localhost on the EC instance, but this did not work because (i think) LB has to trust this cert before it will receive a 200 back.
How to handle a situation like this?
Comments
Post a Comment