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

0

Hi,

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

That error came up when i tried to add a CNAME (custom domain name) to a Cloudfront distribution. There is a absolutely no chance that there is anything related to that domain on the account in any zone. I see that there are several other tickets like mine and in some of them answer is that anybody can create CNAME with any domain and exactly that error will come up. I also noted that the domain was in AWS a few years ago when managed by someone else. So i presume that a cloudfront distribution is still in someone's AWS account and that stops me add it as a CNAME although I even have the domain in the same account on ROUTE 53. Is there a way out ? Or cloudfront is banned for that domain until someone somewhere deletes his Cloudfront distribution?

bgbs
질문됨 일 년 전237회 조회
1개 답변
0

The following command may be used to check if CNAME is being used.
If the domain is being used outside of your control, you would not be able to use that domain.

aws cloudfront list-conflicting-aliases \
  --distribution-id YYY \
  --alias 'www.example.co'

https://repost.aws/knowledge-center/resolve-cnamealreadyexists-error

profile picture
전문가
답변함 일 년 전
  • I have a similar issue, and this command won't work for me, because I've not been able to deploy cloudfront at all, given the "conflicting" CNAME which apparently exists some where.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠