Locked out of AWS root account - MX records not set up after migrating domain to Route 53

Question

Issue:
I can’t log in to my AWS root account (******@ming-group.de) because AWS sends verification codes to this email, but I’m not receiving them.

Background:

Recently migrated ming-group.de from Jimdo to Route 53 (DNS is working).

Forgot to set up MX records in Route 53 → emails are not being delivered.

Google Workspace was previously linked to Jimdo, but now emails are not routing.

Cannot access AWS console to fix MX records without the verification code.

What I’ve tried:

Submitted AWS account recovery forms (no response yet).

Checked spam/junk folders – no AWS verification emails.

No SMS/backup method available for this account.

Question:

Is there any alternative way to verify ownership (e.g., billing details, support ticket)?

Can AWS Support temporarily disable email verification or use a backup contact?

Any workaround to receive the verification code (e.g., temporary MX fix)?

Urgency: Business-critical – need access to update DNS and restore email flow.

re:Post Agent · Answer

This is a challenging situation, but there are a few potential steps you can take to regain access to your AWS root account:

1. Continue pursuing the AWS account recovery process. This is the official channel for addressing such issues, and while it may take some time, it's the most reliable method.

2. Try contacting AWS Support directly through their account support form. Explain your situation in detail, including the fact that you've migrated your domain to Route 53 but can't set up MX records due to the login issue. They may be able to assist you with alternative verification methods or temporarily disable email verification.

3. If possible, set up a temporary DNS zone for your domain using a different AWS account or an external DNS service. This could allow you to quickly set up MX records and potentially receive the verification emails.

4. Check if you have any IAM users with administrative privileges set up in your AWS account. If so, you might be able to log in with those credentials and open a support case from within the AWS console.

5. Verify if there are any other email addresses associated with the account for billing, operations, or security purposes. AWS might be sending notifications to these addresses.

6. If you have any documentation related to your AWS account, such as billing statements or account details, gather this information. It may help in verifying your ownership of the account when communicating with AWS support.

Remember, for security reasons, AWS is generally very strict about account access. They may require substantial proof of ownership before allowing access without the standard verification process. Be prepared to provide as much identifying information as possible when communicating with support.

In the future, to prevent similar issues, consider setting up multiple authentication methods for your AWS account, including SMS or hardware tokens, and ensure you have more than one administrator-level IAM user.  
**Sources**  
[Who can I contact for MFA problem when we can't receive any email for the root account? | AWS re:Post](https://repost.aws/questions/QUVC1Rjnc3RjWaChEFCQW1kA/who-can-i-contact-for-mfa-problem-when-we-can-t-receive-any-email-for-the-root-account)  
[I don't have access to the email for my AWS account | AWS re:Post](https://repost.aws/questions/QUazjrl_LZTMW2e7oly778cA/i-don-t-have-access-to-the-email-for-my-aws-account)  
[Don't have access to root users email id | AWS re:Post](https://repost.aws/questions/QU5fq7hflWQnqiPIXklaPj-A/don-t-have-access-to-root-users-email-id)

Locked out of AWS root account - MX records not set up after migrating domain to Route 53

Relevant content