If you have lost the MFA device for an AWS account root user, AWS offers a self-service path using the account email address and primary contact phone number, and for accounts in AWS Organizations a centralised path that avoids standalone root credentials altogether. This guide sets out which path applies to your situation, what to do when the email inbox or phone is also lost, and how to secure the account afterwards so that losing a single device never locks you out again.
Losing root access is not usually a security incident in itself, but the recovery process touches the most powerful credential in the account, so treat it with the same care. If you suspect someone else has used or changed the root credentials, stop and follow the AWS Root Account Compromise Playbook instead.
This is an independent guide from NHI Mgmt Group, based on AWS's public documentation as of November 2026. It is not sponsored or reviewed by AWS. Product features change, so confirm settings against AWS's current documentation.
Key takeaways
- First try another registered MFA device. AWS lets root and IAM users register up to eight MFA devices of any type, and the sign-in page offers Try another MFA method.
- With no other device, a root user can choose Troubleshoot MFA and then Sign in using alternative factors, which verifies the account email address and then the primary contact phone number.
- AWS's documentation states that if you do not have access to the email and primary contact phone number, you must contact AWS Support.
- For member accounts in AWS Organizations with centralised root access, the management account or a delegated administrator for IAM can perform privileged tasks, including allowing password recovery, without anyone holding the member account's root credentials day to day.
- If the device was lost or stolen rather than broken, change the root password once you are back in. AWS notes that an attacker may also have the current password.
- Prevention is cheap: keep the root email and phone current, use a monitored shared mailbox, and register more than one MFA device.
When you need this
This guide applies when someone legitimately responsible for an AWS account cannot sign in as the root user because one or more of the following is missing:
- The MFA device registered to the root user is lost, broken, wiped or held by a person who has left.
- The email inbox for the root user's address is no longer reachable, for example because the mailbox was deleted or the domain lapsed.
- The primary contact phone number is out of date.
- The root password is unknown and the MFA device is also gone.
Common causes are a departed administrator who registered MFA on a personal phone, a root email tied to one individual's mailbox, and accounts created years ago and never revisited. Root is a non-human identity in practice: it belongs to the account, not to a person, and its credentials should be owned by a role with a documented custodian.
Before you start
- Confirm which kind of account it is. Is it a standalone account, the management account of an organisation, or a member account? The recovery path differs.
- Confirm you are authorised. Get written approval from the account owner or the business unit, and record who is performing the recovery.
- Check whether an IAM or Identity Center administrator still has access. Many root-only tasks never need doing, and an administrator can update some account contact information. AWS notes that if you can still sign in as an IAM user with administrator access, you can update the primary contact phone there.
- Find out what you actually need root for. AWS lists tasks that require root credentials. If your need is not on that list, you may not need to recover root at all right now.
- Rule out compromise. If the root email or password was changed without your knowledge, treat it as an incident.
Which recovery path applies
Use this table to pick the right starting point. It summarises the paths described in the sections that follow and in AWS's documentation.
| Your situation | Start with |
|---|---|
| Another MFA device is registered to root and still works | Path 1: try another MFA method |
| No other device, but you control the root email and the primary contact phone | Path 2: sign in using alternative factors |
| Member account in AWS Organizations with centralised root access enabled | Path 3: privileged tasks from the management account or delegated administrator |
| No device, and the email and phone are both unavailable and cannot be repaired | Path 4: contact AWS Support |
| Root email or password changed without your knowledge | Stop: follow the compromise playbook |
Whichever path you use, finish with the steps in the section on securing the account afterwards. A recovery that leaves the same single device, personal mailbox and stale phone number in place only postpones the next lockout.
Path 1: use another registered MFA device
AWS recommends registering multiple MFA devices so that you keep access if one is lost or broken, and allows up to eight per root or IAM user. If another device was registered:
- Sign in as the root user with the account email address and password.
- On the Additional verification required or Multi-factor authentication page, choose Try another MFA method.
- Authenticate with the other device.
- Once signed in, deactivate or delete the lost device on the security credentials page, and register a replacement.
This is the quickest path and the one you should design for. If it worked, skip to the section on securing the account afterwards.
Path 2: sign in using alternative factors
If the root user has no other usable MFA device, AWS provides a self-service recovery flow that verifies the account email address and the primary contact phone number. Based on AWS's documentation:
- Choose Root user on the sign-in page, enter the account email address and the password.
- On the Additional verification required page, select an MFA method and choose Next.
- Choose Troubleshoot MFA, re-enter the password if prompted, and choose Sign in.
- On the Troubleshoot your authentication device page, choose Sign in using alternative factors.
- Choose Send verification email. AWS sends a message from
[email protected]. Follow the directions in it; check spam or choose Resend the email if it does not arrive. - After email verification, choose Call me now to verify the primary contact phone number. Answer the call and enter the six-digit number shown on the AWS page using the phone keypad.
- After verification, choose Sign in to the console.
If the call does not arrive, AWS suggests choosing Sign in to start again, or contacting support. Treat the verification email with care: anyone who controls the root mailbox and phone can complete this flow, which is why those two channels need the same protection as the MFA device itself.
Once signed in, replace the device. AWS notes that you do not need to replace it with the same type. For a virtual MFA app, remove the account from the app and delete the old MFA device entity before creating a new one. For a FIDO security key, deactivate the old key before enabling a new one. For a hardware TOTP token, contact the token provider; AWS says you can keep signing in with alternative factors until the new device arrives.
Path 3: member accounts with centralised root access
For accounts in AWS Organizations, AWS offers centralised root access for member accounts. AWS describes this as a way to centrally secure access to root user credentials for member accounts and to centrally remove and prevent long-term root user credential recovery. With it enabled:
- You can remove the member account's root password, access keys and signing certificates, and deactivate its MFA.
- AWS states that new accounts created in Organizations have no root user credentials by default.
- Member accounts cannot sign in as root or perform root password recovery unless account recovery is enabled.
- The management account, or a delegated administrator for IAM, can perform privileged tasks on member accounts: remove root user credentials, allow password recovery, remove a misconfigured S3 bucket policy that denies all principals, and delete an SQS resource-based policy that denies all principals.
In this model, "lost root MFA" on a member account becomes a non-event. If the task you need is one of the privileged tasks, run it centrally. If you genuinely need root sign-in, the management account or delegated administrator performs the Allow password recovery privileged task, and the person with access to the member account's root email inbox can then reset the root password. AWS recommends deleting the root credentials again once the root-level task is complete.
AWS also states that the management account or delegated administrators can update a member account's root email, name, contact information, alternate contacts and Regions, and can close member accounts. That gives you a route to repair a lost root mailbox for a member account without contacting support, provided your organisation's administrators still have access. See the AWS Organizations and SCPs Guide for the wider organisation design.
Path 4: when the email or phone is also lost
AWS's documentation is direct: if you do not have access to the email and the primary contact phone number, you must contact AWS Support, using the MFA support contact route linked from the lost or broken MFA page. Expect to prove that you are authorised to act for the account. Prepare in advance:
- The AWS account ID and the root email address on record.
- Evidence of ownership that the business holds, such as billing records and the payment method on file.
- A named contact who is authorised to act for the account, with authority documented internally.
Before you open a case, check whether you can fix one of the two channels yourself, because the self-service flow is faster:
- Phone out of date. If an IAM user with administrator access can still sign in, AWS notes that they can update the primary contact phone number, after which Path 2 may work.
- Mailbox lost but domain still yours. Recreate the mailbox or alias at the same address in your email system, then run Path 2.
- Member account. Use the management account to update the root email or run the privileged tasks in Path 3.
For a standalone account, AWS lists changing the root email address, root password and root access keys among tasks that require root credentials. If both channels are gone and nobody holds root, support is the only route.
Secure the account afterwards
Recovery is the moment to fix the conditions that caused the lockout:
- Change the password if the device was lost or stolen. AWS advises changing the root password after signing in and setting up the replacement MFA device, because an attacker may also have the current password.
- Register more than one MFA device. Use phishing-resistant FIDO security keys where possible, with at least two held by different custodians in separate secure locations.
- Move the root email to a controlled mailbox. Use a distribution list or shared mailbox in a domain your organisation controls, with access logged and limited to named custodians, not an individual's inbox.
- Update the primary contact phone. Use a number owned by the organisation, not a personal mobile.
- Remove root access keys. AWS recommends removing root access keys when no longer needed.
- Adopt centralised root access. For organisations, remove member account root credentials and run root-only tasks centrally.
- Review activity. Check CloudTrail for root sign-in and credential changes during the period the device was missing.
- Use administrators, not root, for daily work. AWS recommends an administrative user in IAM Identity Center instead of root for everyday tasks.
Write the custodian arrangement into a break-glass procedure. The Break Glass Access Procedure Template gives a structure for storage, dual control and testing.
Common failure patterns
- Root tied to one person. The email is someone's personal work mailbox and the MFA is on their phone; when they leave, the account is orphaned.
- A single MFA device. AWS allows up to eight; registering one creates a single point of failure.
- Stale contact details. The primary contact phone points to a number nobody answers, so alternative factors fail.
- Lapsed domains. The root email sits on a domain the company no longer renews, which is both a lockout and a takeover risk.
- Recovering root when it was not needed. Teams go through recovery for tasks an IAM administrator or the management account could have done.
- Skipping the password change. A stolen device is treated as a broken one, leaving a possibly known password in place.
- Leaving restored member root credentials in place. Root credentials recovered for one task are never removed again.
Practitioner checklist
- Account type confirmed: standalone, management or member.
- Authorisation for recovery documented, with the person performing it named.
- Compromise ruled out, or the compromise playbook started instead.
- Another registered MFA device tried first.
- Alternative factors flow completed, or management account route used for member accounts.
- AWS Support engaged only where email and phone are both unavailable and cannot be repaired.
- Lost device deleted and at least two replacement MFA devices registered with separate custodians.
- Root password changed if the device was lost or stolen.
- Root email moved to a controlled shared mailbox and primary contact phone updated.
- Root access keys removed; member account root credentials removed again after use.
- CloudTrail reviewed for root activity during the gap; break-glass procedure updated and tested.
Standards and references
- AWS IAM User Guide: Recover an MFA protected identity in IAM (lost or broken MFA device)
- AWS IAM User Guide: AWS account root user (centralised root access and tasks that require root)
- CISA: Implementing Phishing-Resistant MFA
- MITRE ATT&CK: Valid Accounts: Cloud Accounts
- NIST SP 800-53 Rev 5: IA-2 Identification and Authentication, AC-2 Account Management, AC-6 Least Privilege
- CIS: Critical Security Controls v8.1
Related NHI Mgmt Group resources: AWS Root Account Compromise Playbook · Break-Glass Account Guide · AWS Organizations and SCPs Guide · AWS IAM Identity Center Guide