A few weeks ago, we created a new AWS account and added it to an organization managed by our existing five-year-old AWS account. Shortly afterward, both accounts were marked as unverified. We can no longer use the new account, and access to our production account has effectively been disrupted as well. We opened support cases for both accounts, but they have remained unassigned for more than a week. Has anyone experienced this kind of verification issue, or know what might be causing it and how to get AWS support to respond faster?
1 Answer
This needs to be handled through AWS Support as an account-verification and production-impacting issue. Make sure both cases clearly identify the business impact, reference the related account IDs, and request that they be linked and escalated. If the cases remain unassigned, opening or updating the case through every available support channel may help get them routed to the appropriate account team.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures