I created a new AWS account and completed the payment, phone, and email verification steps. AWS says activation usually takes minutes and may take up to 24 hours, but after more than three days my account is still restricted.
CloudShell cannot create an environment because verification is still in progress, and EC2 instance launches fail at the account level in ap-south-1, including through CloudFormation. Other services, including RDS, S3, IAM, ECR, and VPC, were able to provision before the stack rolled back when the EC2 step failed.
I opened an Account and Billing support case and then submitted a separate Account Activation or Account Verification case. The second case was automatically marked as a duplicate and redirected to the first. I have replied requesting human escalation and provided the EC2 request IDs and CloudFormation timestamps, but so far I have only received automated verification responses.
I checked the root account email and spam folder and have not received a request for documents or additional verification. Is a delay this long normal for a new account? Is there an escalation path beyond replying to the existing case, or is there anything I should verify or do while waiting?
3 Answers
Three days is longer than usual, but verification backlogs can happen depending on the region, payment method, or automated risk checks. Since services such as S3 and RDS work while EC2 is blocked, this may be an EC2 or account-activation hold rather than a complete suspension. Keep replying to the existing support case, clearly ask whether anything is pending from you, and include the relevant request IDs and timestamps. Checking whether the same launch works in another region may also help determine whether ap-south-1 is part of the problem.
Try a very small EC2 launch through the normal console in a different region, such as us-east-1, while also confirming that the payment card and phone number are fully verified. If it fails in every region, that points more strongly to an account-level review. If it works elsewhere, provide that comparison to support so they can investigate the regional restriction.
This can be caused by an automated fraud or account-risk review, even when the signup steps appear complete. It may take several days for a human review, and the automated responses do not necessarily mean you need to submit more information. Continue using the existing case rather than opening many duplicates, and explicitly ask support to confirm whether the account is awaiting internal verification or whether they need documents or another action from you.
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