![[The AI Show Episode 142]: ChatGPT’s New Image Generator, Studio Ghibli Craze and Backlash, Gemini 2.5, OpenAI Academy, 4o Updates, Vibe Marketing & xAI Acquires X](https://www.marketingaiinstitute.com/hubfs/ep%20142%20cover.png)
![[FREE EBOOKS] The Kubernetes Bible, The Ultimate Linux Shell Scripting Guide & Four More Best Selling Titles](https://www.javacodegeeks.com/wp-content/uploads/2012/12/jcg-logo.jpg){kind=logo}
![From drop-out to software architect with Jason Lengstorf [Podcast #167]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743796461357/f3d19cd7-e6f5-4d7c-8bfc-eb974bc8da68.png?#)
.png?#)
.jpg?#)
_Christophe_Coat_Alamy.jpg?#)
 (1).webp?#)
![Rapidus in Talks With Apple as It Accelerates Toward 2nm Chip Production [Report]](https://www.iclarified.com/images/news/96937/96937/96937-640.jpg)
AWS CloudFront CNAME Conflict – “One or more of the CNAMEs you provided are already associated with a different resource”
I am trying to create a new CloudFront distribution and associate the alternate domain name app.example.com with it. Additionally, I have a valid ACM SSL certificate issued for app.example.com in N.Virginia. However, when I attempt to save the CloudFront distribution, I receive the following error: "One or more of the CNAMEs you provided are already associated with a different resource." Troubleshooting Steps Taken: Checked existing CloudFront distributions using the command: _aws cloudfront list-distributions --query "DistributionList.Items[*].{Id:Id,Aliases:Aliases.Items}" --output json_ app.example.com is not listed in any of the CloudFront distributions. Checked for deleted CloudFront distributions (in case the CNAME was retained): _aws cloudfront list-distributions --include-deleted --query "DistributionList.Items[*].{Id:Id,Aliases:Aliases.Items}" --output json_ The domain did not appear in deleted distributions either. Checked Route 53 records: app.example.com currently has: An A record pointing to an internal ALB. A CNAME for ACM certificate validation (which should not cause conflicts). Has anyone faced a similar issue before?
I am trying to create a new CloudFront distribution and associate the alternate domain name app.example.com with it. Additionally, I have a valid ACM SSL certificate issued for app.example.com in N.Virginia.
However, when I attempt to save the CloudFront distribution, I receive the following error:
"One or more of the CNAMEs you provided are already associated with a different resource."
Troubleshooting Steps Taken:
Checked existing CloudFront distributions using the command:
_aws cloudfront list-distributions --query "DistributionList.Items[*].{Id:Id,Aliases:Aliases.Items}" --output json_
app.example.com is not listed in any of the CloudFront distributions.Checked for deleted CloudFront distributions (in case the CNAME was retained):
_aws cloudfront list-distributions --include-deleted --query "DistributionList.Items[*].{Id:Id,Aliases:Aliases.Items}" --output json_
The domain did not appear in deleted distributions either.-
Checked Route 53 records:
app.example.com currently has:- An A record pointing to an internal ALB.
- A CNAME for ACM certificate validation (which should not cause conflicts).
Has anyone faced a similar issue before?
