Skip to content

Account closed for non-payment: root password reset done, now blocked on root MFA (former employee’s device)

-1

Hi AWS Support team,

Update (Oct 12): Root password reset was successful, but we’re now blocked on root MFA, since the device and phone belonged to a former employee. We submitted an MFA support case on Oct 8th and haven’t heard back yet. Any help moving it along would be appreciated, given the closure timeline. This is still a blocker as we are not able to proceed to access the account to take any action!

I'm the DevOps Lead at our company, and I'm asking for help with a suspended account in our AWS Organization. The suspension notice gives today, October 7, 2026 as the deadline to reinstate the account, and we haven't been able to get a response through the normal channels.

Situation

A member account in our organization was suspended on September 7, 2026 for non-payment. We have no console access to the member account or to our consolidated billing payer account. Root password recovery on the member account returns "Password recovery is disabled for your AWS account. Please contact your administrator," which I understand is because root access is managed centrally from the payer account. We want to pay the outstanding balance, but we can't see invoices or reach the Billing console.

Cases opened through the contact form (no reply besides the auto-acknowledgment):

***************: original request with full details ***************: follow-up asking for a callback

What we're asking for:

Someone to review the cases above and contact us. A phone callback would be ideal. A short extension of the reinstatement deadline, or confirmation that resources won't be deleted, while we complete verification and payment. Guidance on regaining root access to the payer account, so we can restore the member account and pay what we owe.

We're ready to verify ownership and pay right away. Thank you for any help.

*Edit: Removed Case ID - Craig M.

3 Answers
0
Accepted Answer

Hello,

I'm sorry for the concern the delay on your case has caused.

I can confirm that your case is currently being attended to. Keep an eye open for correspondence from our Support team.

- Craig M.

AWS
EXPERT

answered a month ago

EXPERT

reviewed 18 days ago

  • Thanks Craig for your help, yes, I did get help and was able to reset the password, but now stuck with MFA. Created a new case yesterday as per the online instructions and awaiting response. "[CASE 179148609200845] [AWS MFA Support Form Submission] " Appreciate your help on this! Thanks, Sreenadh

0

I understand you're facing a time-sensitive situation with an account suspension. Let me provide guidance on how to address this.

For account suspension issues related to billing, you'll need to work directly with AWS through the AWS Support Center. Since you've already opened support cases, the best path forward is to add correspondence to your existing cases through the AWS Support Center at https://console.aws.amazon.com/support/. This ensures your updates are seen by the team handling your situation.

Regarding Organizations and consolidated billing: When a member account is suspended, billing-related actions typically need to be handled through the management account (payer account) of the organization. If you've lost access to the management account, you'll need to work with AWS Support to verify ownership and regain access. The support team can guide you through the account verification process.

For root access recovery in an Organizations setup: The message you're seeing about password recovery being disabled is expected behavior when root access is managed centrally. AWS Support will need to assist with the verification process to help you regain access to the management account.

Since this involves account access and billing matters, these cases require manual review and verification steps that only AWS Support can perform. The support team will need to verify account ownership before they can assist with access restoration or discuss billing details.

If you need faster response times for urgent situations like this, you may want to review your AWS Support plan options, as higher-tier plans include faster response times and phone support for urgent issues. You can add updates to your existing cases through the Support Center to emphasize the time-sensitive nature of your situation.

answered a month ago

AWS
EXPERT

reviewed a month ago

  • That's what I did and no response post creating the online case

0

If this is an AWS Organizations environment, the first thing to establish is whether the affected account is a member account and whether the outstanding charges are being handled through the organization's management/payer account. In a consolidated AWS Organization, the management account is responsible for the organization's consolidated billing and payment obligations. Therefore, the member account's inability to access its billing information does not necessarily mean that payment must be made from the member account itself. If the management account is accessible, I would recommend:

  1. Check the Billing console from the management account.
  2. Identify the outstanding balance associated with the affected account.
  3. Resolve the payment issue immediately.
  4. Verify the member account's status afterward.
  5. If the management account or billing console itself is inaccessible, continue through AWS Account/Billing Support and clearly indicate that the account is suspended and that there is a reinstatement deadline. I would avoid relying on re:Post for the actual reinstatement. This is an account-specific billing/support issue, so AWS Support is the appropriate channel. Also, don't post account IDs, case IDs, invoices, payment details, or other account-identifying information publicly on re:Post.

answered a month 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.