Unable to use domain after transfering to another aws account


I recently transferred a domain from aws account to another aws account using aws cli. Now in route53, Domain name status code is empty. I created a hosting zone but cannot verify my SSL certificate created with certificate manager. I tried to link the domain to a elastic beanstalk URL, but it's also now working. It seems to be some problem with route53, but can't figure it out.

1 Answer

Hello there,

I understand that you transferred a domain from an AWS account to another AWS account using the AWS CLI and now in Route53 the domain name status code is empty and you cannot verify your SSL certificate created with certificate manager.

Common problems that could cause your domain name status code to not show in Route53 include:

  • You didn't click the link in the authorization email
  • The authorization code that you got from the current registrar is not valid
  • "Parameters in request are not valid" error when trying to transfer a .es domain to Amazon Route 53

In order to resolve any of the problems mentioned above, please refer to reference [1].

Please take note that when you transfer a domain from one AWS account to another, Route 53 doesn't transfer the hosted zone that is associated with the domain. DNS resolution isn't affected if the domain and the hosted zone are owned by separate accounts, so transferring the hosted zone is optional. For information about transferring the hosted zone to another AWS account, see reference [2].

If your domain is unavailable on the internet, please see reference [3] for common reasons and their resolutions.

Common problems related to not being able to verify your SSL certificate include:

  1. The certificate is not valid for the name of the server
  • Resolution would be to check the domain that you're accessing, and then check the domain names included in your certificate. You can view the domain name using your browser and by checking the certificate details. The domain in the URL must match at least one of the domain names included in the certificate.
  1. The certificate is expired
  • Resolution would be to issue or import a new certificate. After a new certificate is issued, confirm that your DNS records are pointing to the AWS resource, such as a load balancer, where the ACM certificate is used. Please see reference [4] for more information.
  1. The SSL/TLS certificate for the website is not trusted
  • Resolution would be to update your browser to the latest version, or try to access the domain from a different computer and browser. If you imported a self-signed certificate using AWS Certificate Manager (ACM), then some browsers can't trust the certificate. Please see reference [5] for more information.
  1. Your connection is not fully secured
  • To resolve this error, update your source code to load all the resources on your page over HTTPS.

If none of the above mentioned probable causes and resolutions are not working, you can try to transfer your domain to another registrar and you can get the authorization code through the Route53 console by following the steps below:

  1. Navigate to the Route53 console page
  2. Click on ‘Registered domains’ section on the left side navigation pane in the Route 53 console.
  3. Click on the domain name to pull up the domains information page.
  4. Click on ‘Get code’ under the ‘Authorization Code’ section


[1] https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-domain-transfer-failed.html

[2] https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-migrating.html

[3] https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-domain-unavailable.html#troubleshooting-domain-unavailable-transferred-domain-wrong-name-servers

[4] https://docs.aws.amazon.com/acm/latest/userguide/troubleshooting-renewal.html

[5] https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html

I hope this helps but if it does not, you can provide your domain name for a further investigation.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions