Select Language:
If you’re trying to launch an EC2 instance and see a vCPU limit error, you’re not alone. Many new AWS accounts, especially those on the Free Tier, encounter this issue.
Here’s what’s happening: Your account has a vCPU limit of just 1, but you’re attempting to start a T3 instance that needs 2 vCPUs. Because of this, AWS blocks the launch, and you receive an error message.
To fix this problem, you have some simple options:
First, consider choosing a smaller instance type. If you want to stay within the Free Tier, use t2.micro or t3.micro instances. Both of these have only 1 vCPU and are usually eligible for Free Tier accounts created before July 15, 2025, as long as your account is less than a year old.
Second, you can request an increase to your vCPU limit. This can be done through the AWS Service Quotas console. Just go to the Amazon EC2 section and find the quota related to the instance type you want to run. Request an increase there, and AWS may approve it depending on your account and usage.
Third, check if the region you selected supports the instance type. Not all AWS regions offer every instance. If t2.micro isn’t available where you are, try t3.micro, which is often available as a Free Tier option.
Lastly, review your Free Tier eligibility. For the first 12 months, the Free Tier typically includes 750 hours per month of t2.micro or t3.micro instances, depending on availability in your region.
Remember, while you’re on the Free Tier, limits are in place to prevent unexpected charges. These limits include the number and types of instances you can run at the same time.
If you follow these steps, you should be able to launch your EC2 instance without hitting the vCPU limit.





