1 Answer
- Newest
- Most votes
- Most comments
-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.
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year 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?
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
Hi Mark
I've also run into this issue -
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
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.