I've encountered a frustrating situation with AWS where my account has been suspended for verification, and as a result, Route 53 has also been suspended. This has led to a big issue: my domain is suspended, which means there's no MX record available. Consequently, I'm unable to change the root password because the original email associated with the account isn't accessible anymore. This is preventing me from following AWS's guidance and puts me at risk of losing my client account altogether. This doesn't seem logical!
4 Answers
One important lesson to take away is to never host your email service within the same account that manages access to it. It can create a tricky situation similar to what you're facing right now.
A simple tip: avoid using an email hosted on AWS for your AWS account. It can lead to complications like the one you’re experiencing.
We want to help you, but we need more details. If you can provide a case ID, that would really help us assist you better. Also, just a thought: it might be helpful for AWS to implement a backup recovery email for root accounts that isn't hosted in Route 53 to avoid these scenarios. It seems like a common issue here!
I've been in a similar situation, and it took me two months to regain access. Even when I had the right phone number and verified details, it was a hassle. I eventually moved my DNS to CloudFlare to prevent this from happening again.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads