- Newest
- Most votes
- Most comments
That means that at least one of those alias names is already associated with another CloudFront distribution. CloudFront has to have one distribution to route all incoming requests for a given name to, so you first have to remove the aliases from the old distribution and only then add them to this new one.
Hi @Sachim. I ran into a similar issue. I found this thread was very helpful and solved my issue. Any Amplify apps that you create initiate an "internal Cloudfront distribution". My AccountID was the same as yours in the CL readout "******200621".
Read this solution for all of the details: https://repost.aws/questions/QU_JCUpVWcQ1SB9O1CW3tT3Q/aws-cloudfront-one-or-more-of-the-cnames-you-provided-are-already-associated-with-a-different-resource
A big thanks to @BazzieB_AWS for the solution!
Best of luck!!
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 19 days ago
Yea, I saw other re:post's with similar comment, however I only have 1 CF distribution on my account, the distributionID and accountID on the "list-conflicting-aliases" commands are not my accountID or my CF distributionID. Thanks
CloudFront is a global CDN. It doesn't matter which account is using the DNS names. Each name can only be routed to one distribution globally. If someone else is using the name for their CloudFront distribution, you cannot use it for yours, and vice versa.
I see, I did purchase the domain name on Route 53 though, so does that mean someone else is using the same domain name on their Cloud Front distribution? Thanks
@Sachin Yes, that's what it means. It might be an old CloudFront distribution from the time they used to own it. They wouldn't be receiving any traffic to it, since you control the DNS now, so it might not be so difficult to persuade them to delete their distribution.