Contradictory requirement: Free account Instance Launch fails due to T2.micro not eligible for any region and t3.micro eligible for Free plan but rejected at Instance Launch due to more than 1 vCPUs.

Question

I created a new account yesterday   for a Linux  virtual server selecting the default configuration to play around and the services. T3.micro with 2vCPUs shows Eligible for Free Plan.
Launching an instance results in:
* Initializing requests  Succeeded
* Creating security groups  Succeeded
* Creating security group rules  Succeeded
* Launch initiation ** Failed**

The error message on the top is , "Instance launch failed. You have requested more vCPU capacity than your current vCPU limit of 1 allows for the instance bucket that the specified instance type belongs to. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit."

The t2.Micro option to select 1vCPU is disabled. The message that pops up when the mouse hover on t2. micro is:
 "This instance is not eligible under Free Plan. Upgrade your account to access this type"..  I selected the default offering with 2vCPUs.

My account is stuck  two contradictory  requirements.

My work is blocked. Please help at your earliest convenience. Thanks.

re:Post Agent · Answer

It appears you're facing a common issue with AWS Free Tier EC2 instance creation. Let me clarify what's happening:

The error message indicates you've hit a vCPU limit of 1 for your account, which is a default setting for new AWS accounts, especially those on the Free Tier. This is designed to protect users from unintentionally incurring costs.

There seems to be some confusion about instance types:

1. T3.micro instances typically have 2 vCPUs, which exceeds your current account limit of 1 vCPU.

2. T2.micro instances (which have 1 vCPU) should be Free Tier eligible, but you're seeing a message suggesting they're not available in your region. This is because not all AWS regions offer t2.micro - in some regions, t3.micro is the Free Tier eligible option instead.

To resolve this issue, you have a few options:

1. Request a quota increase: Visit the AWS Service Quotas console, navigate to the Amazon EC2 section, and request an increase for your vCPU limit. This would allow you to use the t3.micro instance.

2. Try a different region: Some regions may have different instance type availability. You might find t2.micro available in another region.

3. Check your region's Free Tier eligible instances: Make sure you're selecting an instance type that's both Free Tier eligible and available in your chosen region.

4. Verify your account is fully verified: Sometimes new accounts have limited access to certain instance types until the verification process is complete.

This situation isn't actually contradictory - it's a combination of regional availability of instance types and default account limits that's causing the confusion.  
**Sources**  
[problem in creating Amazon EC2 instance | AWS re:Post](https://repost.aws/questions/QU21Q69g5gSC-AutE6kiH3iw/problem-in-creating-amazon-ec2-instance)  
[Unable to create more than one EC 2 instance | AWS re:Post](https://repost.aws/questions/QUMjfyszsyRIuCAoAa6O9zgg/unable-to-create-more-than-one-ec-2-instance)

Contradictory requirement: Free account Instance Launch fails due to T2.micro not eligible for any region and t3.micro eligible for Free plan but rejected at Instance Launch due to more than 1 vCPUs.

Add your answer

Relevant content