Help for owners
The person who set up our cloud account has left and nobody has the main login
Short answer
On AWS the owner of the account is the root user, tied to the email address used at sign-up. If you control that mailbox you can reset the password yourself. If you do not, try to regain the mailbox first, and only then contact AWS Support. Do not create a second account as a workaround.
Does this sound like your situation?
- The person who created our cloud account has left the company.
- The account is registered to a personal or old email address.
- I can log in as a normal user but cannot change billing or close things.
- A security prompt asks for a code from a phone or app that nobody has.
- I do not know which cloud account our website and app actually run on.
Why does this happen?
The account was opened with one person's email
AWS states that the email address and password given at sign-up are the root user credentials. If that address belonged to a freelancer or employee, the whole account is tied to a mailbox you may not control.
Confirmed by docs.aws.amazon.com
A password reset needs the mailbox
AWS lets the root user reset a forgotten password from the console, but the reset link goes to the email address on the account. Without access to that mailbox the reset cannot be completed.
Confirmed by docs.aws.amazon.com
A second factor lives on someone's phone
AWS says the root user can recover access only by signing in with another MFA device registered to the same root user, and otherwise has to contact Support. A phone that left with the employee therefore blocks the login.
Confirmed by docs.aws.amazon.com
Everyday logins were separate users
Teams often work through individual user accounts, and these can be disabled when a person leaves. Whoever remains may then have no one with permission to manage users.
Support will not change credentials
AWS states that Support cannot change the credentials of an account. Recovery runs through the email address and the second factor, not through a support request alone.
Confirmed by docs.aws.amazon.com
What can I do about it today?
- Find out which email owns the accountSearch company mailboxes for messages from AWS, which AWS says come from addresses ending in signin.aws or verify.signin.aws.
- Get the mailbox back firstIf the address is on your own domain, your email administrator may be able to restore it or forward its mail to a person you trust. That is the key to everything else.
- Do not open a new account and move things in a rushA second account does not give access to the first, and moving a live system without a plan can cause an outage.
- Do not share passwords in chat or emailWhen access returns, set up named users for each person instead of one shared login.
- Write down what runs thereList the websites, apps, databases, domain and email that depend on the account, so the recovery effort can be prioritised.
When should I bring someone in?
- The registered email no longer exists and the person cannot be reached.
- The second-factor device is lost.
- The account holds production systems and a bill or renewal is coming due.
How do I handle it?
- Establish who legally owns the accountI help you gather the proof of ownership that AWS Support is likely to ask for: contract, invoices and company details.
- Work through the official recovery stepsMailbox first, then the root password reset, then the multi-factor recovery path published by AWS, in the order the documentation gives.
- Never ask for the secretI do not need the password or the code. You or the account owner enter those; I guide the steps.
- After access returns, make it safeA company-owned email address for the root user, a second factor held by two people, named users for the team and a written access list.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can AWS Support just give me access?
AWS states that Support cannot change the credentials associated with an account. They can guide you through account recovery options, but the outcome is their decision.
What if our account is part of an AWS Organization?
AWS notes that member accounts can have centralised root access, with no root credentials of their own. In that case the management account's administrator handles root tasks.
Is it a security risk that a former employee has the login?
It can be, if they still hold the mailbox or the second factor. That is a reason to regain control quickly and then change the credentials.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.