Urgent: Root User MFA Issues - Cannot Access AWS Account Due to Invalid Contact Methods

MFA Codes are not sent via email. They are a OTP code provided by applications such as google authenticator.

Have you followed this post?

https://aws.amazon.com/blogs/security/reset-your-aws-root-accounts-lost-mfa-device-faster-by-using-the-aws-management-console/

I understand the urgency of your situation, and I apologize for the difficulties you're experiencing with accessing your AWS account. This is indeed a critical issue, especially since it involves the root user account. Here's some guidance based on the information provided:

1. Expediting support ticket: Unfortunately, I cannot directly expedite your support ticket. However, given that you're a paying customer and this is a critical access issue, AWS Support should prioritize your case. Make sure you've clearly communicated the urgency and business impact in your support ticket.

2. Alternative verification methods: In cases where the primary MFA device is inaccessible and the alternative contact methods are invalid, AWS has a process for account recovery. However, this process typically requires verification of account ownership, which may involve providing additional documentation or information to AWS Support.

3. SLA for root account access issues: AWS doesn't publicly disclose specific SLAs for root account access issues, as these can vary based on the complexity of the situation and the verification steps required. However, given the critical nature of root account access, AWS Support typically treats these issues with high priority.

In the meantime, here are some additional steps you can take:

1. Double-check that you're using the correct root user email address. Even a small typo can cause issues with receiving MFA codes.

2. If possible, try to access your account using IAM user credentials instead of the root user. If you have any IAM users set up with sufficient permissions, this could provide temporary access to your resources.

3. Prepare any documentation that can prove your ownership of the account. This might include billing information, account creation details, or other identifying information about your AWS resources.

4. Continue to monitor your support ticket closely and respond promptly to any requests for additional information from AWS Support.

5. If you haven't already, consider upgrading your support plan to Enterprise Support for faster response times on critical issues.

Remember, for future security, it's crucial to keep your root user contact information and recovery methods up to date, enable MFA, and use IAM users for day-to-day operations instead of the root user.

I hope AWS Support is able to resolve your issue quickly. In the future, to prevent such situations, regularly review and update your account's security settings, including contact information and MFA devices.
Sources
Troubleshooting AWS account sign-in issues - AWS Sign-In
Activate MFA for your root user - AWS Account Management
Multi-factor authentication for AWS account root user - AWS Identity and Access Management
Community | Understanding Multi-Factor Authentication (MFA)

Hello Mattopo,

I suggest you contact your Technical Account Manager (TAM), as they are the person who can expedite your ticket if you’ve already opened one. Please note that this is AWS re:Post, a public platform, so next time, avoid sharing sensitive information here, such as your AWS Account ID.

Thanks BR

Something similar happened to me

i was having issues pinging my public instance (request time out). Tried to login, the site told me my MFA was incorrect (i triple checked, i did not enter it wrong). after 3 more attempts it went through then it failed to load the dashboard and after a few refreshes it loaded. But i am still having trouble pinging my public instance even after a few restarts

Hello,

Apologies for any concern caused!

I was able to find your case and can share that our team has reached out to you for next steps.

Please follow the guidelines provided & if you need further assistance, reach out directly on your case for Support visibility.

— Elle G.