I recently got locked out of my AWS account because of a $50 unpaid bill. The issue is that this suspension also disabled my Route 53 DNS, which hosts the email for my root account. So, when I try logging in, AWS sends the verification code to an email address I can't access anymore due to the DNS being down.
I've followed all the right steps: I submitted support tickets explaining my predicament, provided alternate contact information, and even escalated the issue via Twitter DMs. However, they keep replying to the dead email account I can't reach. I'm just trying to verify my identity and pay the bill, but support isn't adapting to my situation. Has anyone experienced something similar, where DNS issues prevent login and support continues to use the broken email? How did you resolve it?
2 Answers
Separating your corporate resources from AWS could save a lot of headaches in the future. If your domain is registered elsewhere, you might want to set up a temporary nameserver with the right MX records, change the nameservers at your registrar, and you should be able to receive your emails again.
I feel for you! One approach that might work is creating a new AWS account with a different email, like a Gmail address. You can use that account to open a support ticket and explain your situation. If the domain wasn’t registered with AWS, consider changing the nameservers to point to a different DNS provider temporarily to regain access to your email.
Totally agree! It’s always best to keep things compartmentalized.