AWS IAM Account Frozen

Thank you, I will go ahead and delete that account. Still, I wish AWS would leave my accounts alone and stop making unilateral decisions regarding my account and at least ask me what happened.

This is for the broader audience so that when people search, they'll see this.

With all due respect, what you told me was completely, utterly, 100% incorrect. You went off what the links say and what the test question likely says. I learned a long time ago that vendors' links say one thing, and the real app or device might and more often than not does behave in an entirely different way. I deleted the user account that AWS was blocking and created a new IAM user. Every single one of my security groups, LB's, instances, target groups, you name it, are 100% gone daddy gone. I am now faced with the idea that the last 6 weeks' worth of lab work has been completely erased. I have to now start all of my cert prep for SAA all over again. Please do not dispense of advice just because you read a link. Only dispense of advice when you are 100% sure because you tried it yourself in the wild. I now have to start all over again. I know you meant to help. But you clearly just read the link and never actually tried it. And I was pretty clear on the type of advice I was looking for.

To all others doing cert prep - The way this whole thing started with my IAM account being frozen is one or the other or both of the following:

• Repeated auth failures bec AWS has way too many fields/hoops to jump through before you can logon and it doesn't play well at all with Chrome's autofill. You end up with a hodge podge of your root name and some other items to do with your IAM account.
• Daring to ask for support on AWS. When you do that, it bumps out to some third party paid support that AWS obviously hired since it bumps out from THEIR support page. This is THEIR vendor. The tech and I - a 15 year veteran of AWS - couldn't for the life of us figure out why the instances were failing health check. They don't have screen share so, if you want them to see what you're doing, you have to allow access. I didn't see the harm, so I allowed it and he fixed it. AWS immediately flagged either this or the combination of the 2 as suspicious activity, blocked my IAM user account, and repeatedly ignored my requests to unblock it. AWS Support is a useless organization to do with these issues. They flagged their own vendor as suspicious activity and have never responded to any of my correspondence.

Do NOT use that third party vendor. If have problems, you are strictly, 100% on your own to figure it out.