0

I have a web app on AWS at https://demo.titusgt.com with an AWS Certificate Manager (ACM) certificate.

It was running fine, shown as Secure site in browsers, up until my certificate expired. From the AWS docs I understood that ACM certificates should be automatically renewed, but this didn't happen.

So I went ahead and requested a new ACM certificate following this procedure, the domain owner approved, I associated the new certificate with my Elastic Load Balancer following this procedure, but AWS is still serving the old, expired certificate to my browser, so it shows up as an Insecure site.

Then I provisioned a new certificate with Let's Encrypt, imported it into the AWS Certificate Manager and associated it with my Elastic Load Balancer, but AWS is still serving the old, expired certificate.

I also checked SSLLabs, it says that the certificate is expired.

How can I get AWS to serve the new certificate? Am I missing a step in my setup?

  • 1
    Did you update the certificate on the underlying web servers? – Appleoddity Sep 9 '17 at 23:54
6

demo.titusgt.com is a CNAME to ec2-54-147-110-134.compute-1.amazonaws.com - an individual EC2 instance. As a result, no Elastic Load Balancer is involved in requests to this URL, and as such, it really doesn't matter if you've assigned an SSL certificate to an ELB.

Point the domain at the ELB, or put an SSL certificate directly on the EC2 instance.

|improve this answer|||||
  • Good investigative work. – Appleoddity Sep 10 '17 at 1:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.