I enabled MFA on my cloud root account years ago, but the phone number or device appears to be invalid or no longer available. I currently have no IAM users with administrative access, so I cannot sign in to upgrade my MySQL instance or its operating system. Because the database version entered extended maintenance, my monthly bill increased from roughly $40 to $200. I'm willing to upgrade to MySQL 8.4, but I'm blocked by the unavailable MFA device. I've opened a support case and provided several hours when I could be contacted, but I haven't received useful assistance yet. What is the correct way to recover access, update the environment, and avoid these extra charges?
3 Answers
If the only administrator is the root account, the normal path is account-recovery support for lost or inaccessible root MFA. Be prepared to complete the required identity and ownership checks. Once access is restored, create an IAM administrator, enable a second MFA method or backup process, and avoid using root for everyday work. You can then upgrade the database and operating system, or stop the affected resources if they are no longer needed.
The higher charge is probably related to the database version entering extended support, so recovering access is urgent. Check the support case for the specific account-recovery requirements and make sure the account email, billing details, identity documents, and callback information all match the account records. If the case is stalled, update it through the official support channel and clearly label it as a root-account MFA recovery and billing-impact issue. Support may be able to review the account, but they generally cannot bypass ownership verification.
I’ve already opened a case and exchanged emails, including a window when I could take a call. I’m mainly looking for a way to get the recovery process moving so I can perform the upgrade.
After regaining access, don’t just make the upgrade and leave the account as-is. Create separate admin and operational users, use least-privilege permissions, register multiple MFA options where supported, and keep recovery information current. Also review the billing console and database settings so you can confirm exactly which resource is generating the additional maintenance cost.
That’s the situation: I only have root access and no IAM users. I understand I should have handled the upgrade earlier, but I was already locked out by the unavailable MFA device and am trying to correct it now.