// troubleshooting guide · aws cloudfront
CloudFront SSL Certificate Not Showing (ACM us-east-1)
- Status
- Workaround available
- platforms:
- AWS Console, Terraform, CloudFormation
- updated:
- November 17, 2026
- reports:
- 5
- Method
- how we research
RUNBOOK · aws-cloudfront/ssl-certificate-not-showing3 FIXES
// quick answer
CloudFront only lists ACM certificates from us-east-1 (N. Virginia), and only ones whose names cover your alternate domain names. Request the certificate in us-east-1 with every hostname (apex and www) and validate it via DNS.
Most likely fix: Request the certificate in us-east-1
How to fix it
// try these in order, the most common fix is first
FIX 1Request the certificate in us-east-1
- 01Switch the console region selector to US East (N. Virginia)
- 02Open Certificate Manager > Request > Request a public certificate
- 03Add example.com and *.example.com (or www.example.com)
- 04Choose DNS validation and click Create records in Route 53 if your DNS is there
Did this fix it?FIX 2Wait for the Issued status
- 01Refresh ACM until Status shows Issued (DNS validation can take up to 30 minutes)
- 02Return to CloudFront > distribution > Edit settings and pick it under Custom SSL certificate
Did this fix it?FIX 3Match the CNAME list to the certificate
- 01Compare Alternate domain names on the distribution with the certificate's Domains list
- 02Add missing names to a new certificate if needed
- 03Attach the certificate first, save, then add the extra CNAMEs and save again
Did this fix it?
Symptoms
The Custom SSL certificate dropdown is empty, or saving fails with 'The certificate that is attached to your distribution doesn't cover the alternate domain name (CNAME)'.
Why it happens
- C-01Certificate was requested in another region (e.g. eu-west-1)
- C-02Certificate is still Pending validation
- C-03Certificate SANs don't include the apex or www hostname (wildcard *.example.com doesn't cover example.com)
- C-04Self-signed or untrusted certificate imported
// this guide also covers
- cloudfront certificate not showing
- acm certificate not appearing in cloudfront
- cloudfront certificate doesn't cover alternate domain name
- cloudfront ssl us-east-1
Still not working?
If AWS CloudFront keeps failing, you're not alone. See every AWS CloudFront problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther AWS CloudFront errors
- CloudFront 403 Access Denied With S3 Origin
- CloudFront 403 Error: The Request Could Not Be Satisfied
- CloudFront Invalidation Not Working (Still Serving Old Content)
- CloudFront CORS Error: No 'Access-Control-Allow-Origin' Header
- CloudFront 502 Bad Gateway Error
- CloudFront 504 Gateway Timeout Error
- CloudFront React App 403/404 on Page Refresh
- Why Is My CloudFront Bill So High?