CODEWITHSUNDEEP
amazon-web-servicesssldnsaliasamazon-elb
skmansfield
skmansfield

Reputation: 1443

AWS Certificates Not Secure In Browser

I created an X.509 certificate using the AWS certificate manager.

I used a wildcard designation, *.mydomain.com, and validated it using the AWS DNS.

I then attached it to my Elastic Load Balancer (ELB) along with the instances running my web service.

I then set up a CNAME record in my AWS DNS where the alias name is dev.360yield.admin.mydomain.com and points to the canonical DNS name of the ELB.

I get the "Not secure" notice in the address bar when I use the alias name in the address bar.

The error is the same as if I was using self-signed certificates. I thought that if I used AWS created certificates I would not get this error.

Are my assumptions incorrect?
Did I do something wrong with the setup of the certificate?

Upvotes: 3

Views: 6269

Answers (1)

Julio Faerman
Julio Faerman

Reputation: 13501

As @stdunbar mentioned, this is not by AWS but how SSL wildcards work. For example, in this case dev-360yield-admin.mydomain.com should work, but for dev.360yield.admin.mydomain.com you would need a cert for *.360yield.admin.mydomain.com

Upvotes: 3

Related Questions