Skip to content

EC2 instance create failed via terraform after terraform destroy and terraform re-apply

0

Region: eu-west-2

  1. created a terraform and did apply whihc created instance
  2. i destroyed
  3. when reapplying terraform apply i get Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 4f95d066-7f41-4ece-a2e9-a41ece3e8077, api error Blocked: This account is currently blocked and not recognized as a valid account. Please contact https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create?issueType=customer-service&serviceCode=account-management&categoryCode=account-verification if you have questions. │ this is worng my reion is eu-west-2

The region i am provisioning is eu-west-2. 1st and 2nd time it was successfull. Is it that continous apply/destroy created the problem, kinda blocked the account?

  • What to do: 1. Confirm you’re using the right account and region aws sts get-caller-identity # shows Account ID aws configure get region # should be eu-west-2 Make sure this Account ID is the one you expect and the region is eu-west-2. 2. Check account status (root login)

    •	Billing console → Account settings: if you see “Account closed/suspended/under review”, update payment method and complete any identity checks.
    •	Make sure the AWS Customer Agreement is accepted and the account is fully verified (credit card / phone).
    
    3.	Open a support case (Account & Billing → Account activation / blocked)
    

    Include:

    •	Account ID
    •	Recent RequestId from the error (e.g., 4f95d066-…)
    •	Error text: Blocked: This account is currently blocked and not recognized as a valid account (EC2 RunInstances, HTTP 400).
    

    Only Support can remove the block.

    4.	Rule-outs while you wait
    
    •	If this account is in an AWS Organization, check for SCPs denying ec2:* or RunInstances.
    •	Ensure EC2 is opted-in for eu-west-2 (some services/regions require opt-in).
    •	Verify you’re not using stale creds:
    

    aws sts get-caller-identity # should succeed • IAM permissions alone won’t fix a blocked account — the API will still return 400.

    The Blocked message means the account is suspended/not fully verified. Open an Account & Billing support case to reactivate it; Terraform will work again once the account block is lifted.

asked a year ago454 views

1 Answer
0

Based on the error message you're receiving, your AWS account appears to be blocked, which is preventing you from creating EC2 instances through Terraform. This is not related to the continuous apply/destroy operations you performed.

The error "This account is currently blocked and not recognized as a valid account" indicates there's an issue with your AWS account status. This could be due to several reasons:

  1. Billing issues: There might be outstanding payments or problems with your payment method
  2. Security concerns: AWS may have detected suspicious activity
  3. Account verification requirements: AWS might need additional information to verify your identity
  4. Account inactivity: If you haven't used certain parts of your account for a long time

The fact that the error message references us-east-1 despite your working in eu-west-2 is just part of the standard error message - it's directing you to the support URL which is hosted in the us-east-1 region.

To resolve this issue, you need to:

  1. Check your email for any communications from AWS regarding your account status
  2. Contact AWS Support directly through the link provided in the error message
  3. Open a case under "Account and billing support" (this type of support is available free of charge)
  4. Provide details about your account and the error you're experiencing
  5. Wait for AWS Support to review your case and provide next steps

Only AWS Support can determine why your account is blocked and take the necessary steps to resolve it. While waiting for a response, refrain from attempting to create new resources or making changes to your account.
Sources
[Account Issue] Error: "This account is currently blocked" when creating an EC2 instance | AWS re:Post
Trying to Create a Free Tier EC2 Instance, but I Keep Getting the Error: 'This account is currently blocked and not recognized as a valid account.' | AWS re:Post

answered a year ago

EXPERT

reviewed a year 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.