By using AWS re:Post, you agree to the Terms of Use
AWS re:Postre:Post
/ReservedInstancesLimitExceeded error for a new account of existing organization/

ReservedInstancesLimitExceeded error for a new account of existing organization

0

I created a new AWS account in my AWS Organization. When I try to create a reserved instance in the account I get the following error:

"Error: Your current quota does not allow you to purchase the required number of reserved instances (Status Code: 400; Error Code: ReservedInstancesLimitExceeded; Request ID: 52e35efd-89aa-44ef-9794-026b1176d21b)"

Reserved instance details:

  • Region = us-east-2
  • Instance type = g4dn.2xlarge
  • Offering = standard
  • Quantity = 1
  • Payment terms = All Upfront

It's a new account so I do not have any existing instances in the account in any region.

When I go to limits, it shows that my "Reserved Instances" limit is 20.

I clearly have the limit available for reserved instances, so why am I getting this error?

Topics
ComputeManagement & Governance
Tags
Amazon EC2AWS OrganizationsReserved Instances
AWS-User-1429233
asked 5 months ago147 views
1 Answer
-1

This is an expected behavior for new accounts. To resolve this launch two t2.small instances and wait about 20 minutes. After that your quotas should be increased.

Mark
answered 5 months ago
  • AWS-User-1429233 5 months ago

    Hi Mark,

    I created the new account few day back. I already have one on-demand g4dn.2xlarge instance running for the last 5-6 days on the account.

    Do I still need to run two t2.small instances for 20 minutes?

  • AWS-User-1429233 5 months ago

    Hi Mark,

    I launched two t2.small instances and waited for a couple of hours.

    I am still getting the same error when I try to purchase the reserved instance

  • Alexj12 2 months ago

    Hi Mark

    I've also run into this issue -

    • We've been running 3 different instances for over 400 hours each + RDS instances + Elasticache instances
    • Had a payment of $400+ taken for the first month
    • The same reported reserved instances limit (20)

    And we're still unable to purchase reserved instances. We have a support ticket open to resolve the issue however I think two things are required by AWS

    • Clear documentation if it is not expected new accounts should be able to purchase RIs (or directions to this)
    • A process to ensure they can

    In our case the cost calculator was used to provide a cost estimate to a client and if we're unable to apply reserved instances then we are over budget due to what appears to be an arbitrary limit imposed. We maintain a range of AWS accounts for other clients and have not encountered this issue.

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.

Guidelines for Answering Questions

Relevant questions