CloudFront CNAME already exists error

Question

Hi there!

I'm trying to use my own domain for a CloudFront distribution and keep getting the following error:

**One or more of the CNAMEs you provided are already associated with a different resource.**

I am 100% sure that I didn't use the same name as a  CNAME for another CloudFront distribution in my account.

How can I find out the ARN name of the conflicting distribution? Maybe it was added by another account?

Aleksei · Accepted Answer

The issue was resolve by contacting tech support.

Using the following CLI command I discovered that the conflicting CNAME belongs to a separate account I don't own:

```
aws cloudfront list-conflicting-aliases --distribution-id YourDistributionID --alias YourCNAME
```

Maybe it was a previous domain owner.

The reply was like:
```
{
    "ConflictingAliasesList": {
        "MaxItems": 100,
        "Quantity": 1,
        "Items": [
            {
                "Alias": "****",
                "DistributionId": "*******",
                "AccountId": "******"
            }
        ]
    }
}

```
Then I contacted support and asked to provide me with priority in using my domain's name as CNAME. Then I waited for 4 days and the issue was resolved successfully.

Pravo · Answer

If you don't know the distribution ID, use the [ListConflictingAliases](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_ListConflictingAliases.html) CloudFront API to find partial information about the distribution and the account ID for the conflicting CNAME alias. Then, use [AssociateAlias ](https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_AssociateAlias.html) API to move your CNAME from existing distribution (source distribution) to the new distribution (Target distribution).

***Choose one of the following resolutions based on your scenario:***

1. If your source and target distributions are in the same account, then complete the steps in the Use the AssociateAlias API to move your CNAME section.
    2. If your source and target distributions are in different AWS accounts, then complete the steps in the Deactivate source distribution with the conflicting CNAME section.
    3. If your source and target distributions are in different AWS accounts, and the source distribution can't be deactivated because of downtime to existing traffic, then complete the steps in the Use w**ildcard to move the alternate domain name section.
**

For more details check the link below
https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-error/

Matt-B · Answer

Hi There

Are you using any other services like Amplify or an Edge Optimized API Gateway with a custom domain using this same domain name?  Those services can create an AWS managed CloudFront distribution on your behalf in a separate AWS managed account which could be causing the conflict.

CloudFront CNAME already exists error

Relevant content