This is one of the reasons you should ALWAYS enable MFA on the root account the first thing you opened an AWS account.
That said, now that it already happened, you should change your credential, remove access keys/IAM users and enable MFA.
Then delete all resources you are not using in the accounts. You can see what is costing you money in the Billing Dashboard.
Only then should you close the account.
As to the existing charge, you best course of action is following instructions of the customer service and go through the documents as soon as you can.
Here are some details items you should do in such scenarios.
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- How can I associate a Route 53 health check from a different AWS account to a record set in my account?AWS OFFICIALUpdated a year ago
- EXPERTpublished a year ago
- EXPERTpublished 6 months ago