Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

CloudFront CNAME Already Exists error

by | Jul 26, 2021

Wondering how to resolve CloudFront CNAME Already Exists error? We can help you.

At Bobcares we assist our customers with several AWS queries as part of our AWS Support Services for AWS users, and online service providers.

Today, let us see how our Support Techs resolve this CloudFront issue.


How to resolve CloudFront CNAME Already Exists error?

Typically, error looks as shown below.

One or more of the CNAMEs you provided are already associated with a different resource. (Service: AmazonCloudFront; Status Code: 409; Error Code: CNAMEAlreadyExists; Request ID: a123456b-c78d-90e1-23f4-gh5i67890jkl

It is not possible to use the same CNAME alias for more than one CloudFront distribution.

The error occurs when the CNAME alias you’re trying to add is already associate with another CloudFront distribution.

Today, let us see the steps followed by our Support Techs to move the CNAME to another distribution.

Please note AWS Support can’t associate the same CNAME for more than one distribution.

They can assist you only with switching a CNAME between two distributions or with removing a CNAME from a distribution.

1.Direct your DNS provider to create a TXT record for the distribution that you want to move the CNAME to.

The TXT record is in the following format:

<CNAME alias> TXT <Name of CloudFront distribution that you want to move the CNAME to>

For example, if you’re adding the CNAME alias for your CloudFront distribution named, then direct your DNS provider to create the following TXT record: TXT

If your DNS provider doesn’t allow for identical TXT and CNAME records, consider adding an underscore before the CNAME alias in the TXT record.

2.Then, add a valid SSL certificate to the CloudFront distribution that covers the CNAME that you want to move.

The SSL certificate must also cover any other new CNAMEs that you want to associate with the distribution.

3.After the TXT record is created and you’ve added an SSL certificate to the distribution, contact AWS Support.

Ask that AWS verify the ownership of the DNS domain name and confirm that you can add the CNAME alias to the distribution.

Be sure that you provide a copy of the CNAMEAlreadyExists error message in your case with AWS Support.


[Need assistance with CloudFront? We are available 24*7]


Today, we saw how our Support Techs prevent CloudFront CNAME Already Exists error.



Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.