// 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
Share

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

  1. FIX 1Find the conflicting distribution

    1. 01Run aws cloudfront list-conflicting-aliases --distribution-id TARGET_ID --alias www.example.com
    2. 02Check the masked distribution ID and account it returns
    3. 03If it's yours, remove the alias from that distribution and save
    Did this fix it?
  2. FIX 2Move a subdomain with a wildcard

    1. 01Add *.example.com to the target distribution with a certificate covering it
    2. 02Create the DNS TXT record _www.example.com pointing to the target distribution domain
    3. 03Remove www.example.com from the source distribution, then add it to the target
    Did this fix it?
  3. FIX 3Use AssociateAlias

    1. 01Create the TXT validation record for the domain
    2. 02Run aws cloudfront associate-alias --target-distribution-id TARGET_ID --alias www.example.com
    3. 03The alias moves without deleting the old distribution
    Did this fix it?
  4. FIX 4Contact AWS Support for apex domains

    1. 01Apex domains (example.com) can't be moved with a wildcard
    2. 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 us

Watch AWS CloudFront Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other AWS CloudFront errors

All 12 AWS CloudFront errors and fixes →