Unable to to use domain name on AWS

0

I am attempting to set up my domain name on AWS. I purchased the domain name on hover.com.

I set my doman up on Route53 and pointed my name servers to the provided route53 name servers.

I configured an SSL certificate for mydomain.com and *.mydomain.com and verified them

I set up two buckets one for a cdn and one for my main domain.

I set up a cloudfront distribution pointed to my cdn with no problem and I can access the content there by visiting https://cdn.mydomain.com

However, when I attempt to set up my main domain name with a cloudfront distribution it says that the cname is already in use.

I have checked my cloudfront distributions and under alternate domain names the only one that exists for this domain is cdn.domainname.com

I have other domains set up like this so I know I can have a distribution with both cdn.domainname.com and domainname.com

My best guess as I have run into this on other platforms before is that someone previously owned this domain name and has it configured to a cloudfront distribution on their account. However, since I do not have control of that account there is nothing I can do about it

I have contacted support, however, I have been told they have very limited knowledge and I will have to purchase paid premium support to get any assistance with this.

Does anyone have any suggestions?

demandé il y a 2 mois138 vues
1 réponse
1
Réponse acceptée

Hello.

You must deactivate CloudFront in another account using the steps described in "Deactivate the source distribution with the conflicting CNAME" in the following document.
If you cannot access or disable the AWS account that holds the CloudFront in question, you will need to contact AWS Support.
In your case, I believe you have already contacted free support, but since this is a technical issue, I think you will need paid support.
https://repost.aws/knowledge-center/resolve-cnamealreadyexists-error

If you don't have access to the account that contains the source distribution or you can't deactivate the source distribution, then contact AWS Support.

I think the only thing left to do is to use another subdomain.

profile picture
EXPERT
répondu il y a 2 mois
profile picture
EXPERT
vérifié il y a 2 mois
profile picture
EXPERT
Steve_M
vérifié il y a 2 mois
  • Yea that is what I was afraid of. I will probably just move to another cloud provider then. Its not worth me paying for a service that should just be free on any reasonable platform

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions