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 example.com for your CloudFront distribution named d123.cloudfront.net, then direct your DNS provider to create the following TXT record:

example.com TXT d123.cloudfront.net

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]

Conclusion

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