// troubleshooting guide · aws cloudfront
CloudFront CNAMEAlreadyExists Error
- Status
- Workaround available
- platforms:
- AWS Console, AWS CLI
- updated:
- November 17, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · aws-cloudfront/cname-already-exists4 FIXES
// quick answer
CNAMEAlreadyExists means another distribution (possibly in another AWS account) already uses that alternate domain name. Remove it from the old distribution, move it with a wildcard or the AssociateAlias API, or ask AWS Support for apex domains you can't access.
Most likely fix: Find the conflicting distribution
How to fix it
// try these in order, the most common fix is first
FIX 1Find the conflicting distribution
- 01Run aws cloudfront list-conflicting-aliases --distribution-id TARGET_ID --alias www.example.com
- 02Check the masked distribution ID and account it returns
- 03If it's yours, remove the alias from that distribution and save
Did this fix it?FIX 2Move a subdomain with a wildcard
- 01Add *.example.com to the target distribution with a certificate covering it
- 02Create the DNS TXT record _www.example.com pointing to the target distribution domain
- 03Remove www.example.com from the source distribution, then add it to the target
Did this fix it?FIX 3Use AssociateAlias
- 01Create the TXT validation record for the domain
- 02Run aws cloudfront associate-alias --target-distribution-id TARGET_ID --alias www.example.com
- 03The alias moves without deleting the old distribution
Did this fix it?FIX 4Contact AWS Support for apex domains
- 01Apex domains (example.com) can't be moved with a wildcard
- 02Open a support case with proof of domain ownership if you can't access the source account
Did this fix it?
Symptoms
Saving the distribution fails with 'One or more of the CNAMEs you provided are already associated with a different resource'.
Why it happens
- C-01The domain is still listed on an old or disabled distribution
- C-02Another AWS account (old agency, previous owner, Amplify app) holds the alias
- C-03A wildcard alias on another distribution overlaps the name
// this guide also covers
- cloudfront cnamealreadyexists
- cname already associated with a different resource cloudfront
- move alternate domain name cloudfront
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 usThe same problem in other apps
All not loading, error messages & connection guides →
Cloudflare Error 521: Web Server Is Down (Cloudflare)
Fastly Error: Unknown Domain (Fastly)
Google Cloud Quota Exceeded Error (Google Cloud)
Netlify Page Not Found on Refresh (SPA 404) (Netlify)
Other 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 SSL Certificate Not Showing (ACM us-east-1)
- CloudFront 502 Bad Gateway Error
- CloudFront 504 Gateway Timeout Error
- CloudFront React App 403/404 on Page Refresh