- Newest
- Most votes
- Most comments
I understand you're facing a challenging situation with your blocked AWS account. When an account is blocked due to unrecognized activity, the resolution process can take some time as AWS needs to thoroughly review the situation to ensure account security and compliance with their terms of service.
The duration for resolving such issues can vary depending on the complexity of the case and the current workload of the AWS security team. While there's no fixed timeline, it typically takes a few days to a week for the security team to review and make a decision. In some cases, it might take longer if additional information or verification is required.
Since you've already explained the situation to the support team and they've submitted it for review by the security team, the best course of action is to:
- Be patient and wait for the security team to complete their review.
- Keep an eye on your email for any communications from AWS. They may request additional information or clarification.
- If you haven't already, ensure that all your account details and contact information are up to date.
- If you don't hear back within a week, you may want to follow up with AWS support for a status update.
In the meantime, it's advisable not to attempt creating new resources or making changes to your account until the issue is resolved. Once the security team completes their review and is satisfied with their findings, they will take the necessary steps to unblock your account and restore full functionality.
For future reference, when implementing autoscaling or any automated processes that interact with AWS services, it's a good practice to review AWS's best practices and service limits to ensure your activities don't trigger security alerts.
Sources
Your account is currently blocked. | AWS re:Post
My AWS ACCOUNT IS BLOCKED | AWS re:Post
[Account Issue] Error: "This account is currently blocked" when creating an EC2 instance | AWS re:Post
Relevant content
- asked 3 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago