Skip to content

EC2 RunInstances returns "Blocked - not recognized as a valid account" on a multi-year-old account

0

Multi-year-old account. ec2:RunInstances returns: "Blocked - This account is currently blocked and not recognized as a valid account."

Reproduced with root credentials in two regions (us-east-1 and us-west-2), for both t3.micro and r7i.2xlarge.

In the same session CreateVolume, CreateSecurityGroup and ImportKeyPair all succeed - only RunInstances is blocked. describe-account-attributes shows max-instances 20 and a default VPC, so this is not a quota issue.

Billing is settling normally and there is no verification banner in the console.

Support case open about 9 days with no response (Basic plan, email only). Account ID and case ID available on request.

Sample RequestId: 1c671dd3-e078-43fc-bd1c-b7838d07ca0d

Is there any way to get a blocked-account case reviewed other than waiting on a Basic-plan email case?

asked a month ago133 views

2 Answers
0

Hi there,

I'm sorry to hear that you've experienced this issue with your EC2 RunInstances being blocked.

I can understand your need to have this resolved & I've passed along your concerns internally.

You'll receive updates through your case, so continue monitoring your correspondence.

— Aimee K.

AWS
EXPERT

answered a month ago

EXPERT

reviewed a month ago

-1

The error message you're encountering indicates that your account has been flagged or restricted specifically for launching EC2 instances, even though other EC2 API operations are working normally. This type of selective block typically occurs when AWS's automated systems detect unusual activity patterns or potential policy violations related to instance launches.

Since you have a Basic Support plan, your primary channel is indeed the AWS Support Center. However, given that you've been waiting 9 days without response, here are your options:

First, add a new correspondence to your existing case through the AWS Support Center at https://console.aws.amazon.com/support/. Sometimes adding new information or bumping the case can help move it forward in the queue.

The fact that other EC2 operations succeed while only RunInstances is blocked suggests this is an account-level restriction rather than a technical or quota issue. These restrictions typically require manual review by AWS teams and cannot be resolved through standard troubleshooting steps. Unfortunately, there's no self-service way to remove such blocks—they require AWS Support intervention.

Continue working through the AWS Support Center for resolution, as that's the official channel for account restriction issues.

answered a month ago

AWS
SUPPORT ENGINEER

reviewed a month ago

AWS
EXPERT

revised a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.