1 Answer
- Newest
- Most votes
- Most comments
-1
This is expected behavior and not a bug on the AWS console. The domain in Route 53 is independent of the domain in Cloudfront. The alternate domain name for a Cloudfront distribution needs to be unique. When you try to add an alternate domain name to a Cloudfront distribution but the alternate domain name is already in use on a different distribution(across any AWS Account), you get a CNAMEAlreadyExists error (One or more of the CNAMEs you provided are already associated with a different resource).
There is a process you can follow the move the domain from source distribution to a target distribution. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-move
Hope this helps
answered a year ago
Relevant content
- Accepted Answerasked 6 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
I understand that, but how can I CNAME the domain with a cloudfront in my AWS account? I have no access to the other company's AWS account. They don't own the domain anymore, so there's no point in having it attached to their cloudfront.
Are you saying the only way is to contact the other company?
In that case, you have 2 options.
PS: There is no way for you to know if the source distribution is in DISABLED state, so its a one time trial and error process.
Hey,
Thank you for the suggestions.
Just tried 1, it didin't work unfortunately.
Much appriciated, Ryan
Hey Ketan - Any update here? I'd love to use AWS for this domain. However, I cannot associate the domain with a Cloudfront instance, and I don't have access to the other company's AWS to disassociate the domain. I would be forced to use an alternative service like GCP here.
Can you help?