CNAME SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

CloudFront: CNAMEAlreadyExists / alternate domain name not covered by the certificate (InvalidViewerCertificate)

Adding a custom domain to CloudFront fails because the name is in use elsewhere or the certificate doesn't cover it.

Exact message you may see One or more of the CNAMEs you provided are already associated with a different resource.InvalidViewerCertificate: To add an alternate domain name (CNAME) to a CloudFront distribution, you must attach a trusted certificate that validates your authorizationCloudFront alternate domain name certificateThe certificate that is attached to your distribution doesn't cover the alternate domain name
Seen on: AWS SSL

Meaning

The certificate (ACM, us-east-1) must include the alternate domain name in its SANs, and a CNAME can only belong to one distribution at a time (move it, or use the "associate alias" feature). Create DNS records pointing to the distribution domain once accepted.

Common causes

  • Certificate SANs don't include the CNAME
  • CNAME already used by another distribution/account
  • Wildcard doesn't cover the apex
  • Certificate not in us-east-1
  • Certificate not issued yet

⚡ Quick fix

  1. Use a certificate that includes the domain
  2. Remove the CNAME from the other distribution or associate the alias
  3. Ensure the certificate is ISSUED in us-east-1

Detailed fix by platform

Shell

  1. aws cloudfront list-distributions --query "DistributionList.Items[?Aliases.Items!=null].[Id,Aliases.Items]"

How to diagnose

  1. SAN — Includes CNAME?
  2. CNAME — In use elsewhere?
  3. Region — us-east-1?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionALB listener — ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete (SSL / TLS)ALB listenerapex — Wildcard certificate *.example.com doesn't cover example.com (the bare domain) (SSL / TLS)apexAWS_CA_BUNDLE — AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy) (SSL / TLS)AWS_CA_BUNDLEDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoM365 DKIM — Microsoft 365 DKIM: selector1/selector2 CNAME records not published (can't enable DKIM signing) (Email / SMTP)M365 DKIMsecurity policy — Old clients can't connect to the AWS load balancer: security policy disables TLS 1.0/1.1 (or requires it) (SSL / TLS)security policySES SMTP — Amazon SES SMTP: 535 Authentication Credentials Invalid (IAM user vs SMTP credentials, region) (Email / SMTP)SES SMTPCNAME

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.