title: AWS ACM wildcard ssl certificate not working on domain
body: <p>I created a SSL certificate for my site using Amazon Certificate Manager. The certificate is for *.example.com. I have then attached this certificate to my ELB and have left the instance protocol as http. So SSL chain is only between the client and ELB.
  I have two A records in Route53. One for example.com one for www.example.com. Both of these are aliased to ELB. When I do <a href="https://www.example.com" rel="noreferrer">https://www.example.com</a> it works perfect. But when I do <a href="https://example.com" rel="noreferrer">https://example.com</a> I get the following error in FireFox:</p>
  
  <p>"example.com uses an invalid security certificate. The certificate is only valid for *.example.com Error code: SSL_ERROR_BAD_CERT_DOMAIN"</p>
  
  <p>Shouldn't the certificate *.example.com work for the address example.com? Am I missing something?</p>
  
  <p><strong>EDIT May 31, 2016</strong></p>
  
  <p>Thank you to Steffen Ullrich for setting me on the right track.  The problem is when using the AWS Certificate Manager (ACM) in the console (web browser) there is no option to add the alternative names.  For those having the same problem you need to use CLI (command line interface).  A quick web search for "Install AWS CLI" will give you all the information you need to complete the installation.  Once CLI is installed then you can run the ACM commands.  Here is a link to the documentation:</p>
  
  <p><a href="http://docs.aws.amazon.com/cli/latest/reference/acm/request-certificate.html" rel="noreferrer">http://docs.aws.amazon.com/cli/latest/reference/acm/request-certificate.html</a></p>
  
  <p>The command I used was:</p>
  
  <p>aws acm request-certificate --domain-name www.example.com --subject-alternative-names example.com</p>
  
  <p>Once the request was approved I was able to see the SSL certificate in the ACM web interface.  I installed it and everything working like a charm now!</p>