1 Answer
- Newest
- Most votes
- Most comments
0
Hi, From the screenshot, the optional alternative CNAME (noa-updates.com) matches it in the certificate. For the CloudFront distribution, please check if there are other domains listed. The error "The certificate that is attached to your distribution doesn't cover the alternate domain name (CNAME) that you're trying to add" normally happens when some domain names in the distribution are not included in the certificate.
answered 6 months ago
Relevant content
- Accepted Answerasked 10 months ago
- asked a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
Hi Feng,
Thanks for your reply. I have moved on from this error, however the underline cause was the fact that I was attempting to use a self signed key with cloudfront, which is not allowed. The self signed key did in fact cover the domain, and there werent any other domain conflicts, it just clearly failed to extract the data from the SSL Cert.
Would have been nice to get a verbose error suggesting as such, but it does seem like error messages on AWS are just generally a bit rubbish.