While launching 2nd instance getting below error
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.
First, please note that the AWS Free Tier is a billing discount. It does not impact your ability to use any services. If the resources you use are within the limits imposed by the AWS Free Tier, you simply won't be charged for those resources. Thus, the AWS Free tier is not the cause of this error.
From On-Demand Instances - Amazon Elastic Compute Cloud:
There is a limit on the number of running On-Demand Instances per AWS account per Region. On-Demand Instance limits are managed in terms of the number of virtual central processing units (vCPUs) that your running On-Demand Instances are using, regardless of the instance type.
You did not tell us what Instance Type you are running, or attempted to run, but it sounds like you have exceeded this vCPU limit. This is more likely to happen with large or expensive instance types, or instance types that use GPU resources. You can view the limits in the Amazon EC2 management console by clicking Limits and then searching for vCPU.
If this is impacting your use of AWS, you can request an increase to these default limits.
See: Calculate a vCPU limit increase request for an Amazon EC2 On-Demand Instance
Related
I'm getting ready to launch a mobile app that I have hosted on AWS with an EC2 instance. ($0.0464 per On Demand Linux t2.medium Instance Hour).
This past month I was charged $112 for the EC2 usage, but only had a handful of internal users testing the private version of the app. It's a fairly simple app, not anything that should require a lot of computing power.
So what I'm wondering is if 10 users and dev team costs $112/mo, what happens if I get 1,000 users, or 10k users? Would the cost increase 100x, 1000x? I can't imagine getting auto-billed for $112,000 for a month of service with a small user base like 10k users.
Thanks for any help and guidance, I don't know much about AWS.
Here are the details of my billing for last month:
The billing page shows 2219 hours of t2.medium during this billing month.
That is the equivalent of 92 days. So, it might be 3 instances running for a full month.
Amazon EC2 is charged when the instance is in the Running state. If you are not using an instance, you can Stop the instance. The attached disks (EBS) will still be charged, but there will be no charge for the instance itself.
The charge is not based on the number of users, nor how 'busy' the instance is. It is simply charged when the instance is 'running'. This is because computer resources are exclusively assigned to instances (CPU, RAM) that nobody else can use.
Bottom line: Stop instances that you don't need. Use the smallest instance type for your use-case to reduce costs.
If you were not aware of the charges involved, you can contact AWS Customer Service and request a refund.
FYI, the T2 and T3 family are great for workloads that occasionally 'burst' but then have low-usage periods, but they are not great for sustained workloads. See: Burstable performance instances - Amazon Elastic Compute Cloud
I am getting this error Master Instance Group: Exceeded EC2 Instance Quota, when I create a new cluster on Amazon EMR with 1 Master node only or 1 Master and 2 Core nodes. However, there are no EC2 instances running on my account.
What should I do? I raised a ticket, asking if I can get a quicker solution here.
In your case I think you are trying to access a new region or new instance type, AWS sometimes does that when you are in free tier, they allow access to 2-3 regions or free instance types only. Then you have to request access from AWS by raising a case.
But in Normal scenario, this is what happens:
You may face an error like Exceeded EC2 Instance Quota while you are trying to spin up new instances either standalone or in cluster.
This error is caused because you have hit the limit on number of instances allowed in your AWS account.
This limit is region and instance size specific. To get rid of this error you will have to request Amazon to increase the EC2 instance limit.
Requesting a limit increase is simple. Below are the steps:
Most service limit increases can be requested through the AWS Support Center by choosing Create Case and then choosing Service Limit Increase.
Most service limits are specific to a particular AWS Region, so be sure to submit a request for each Region you plan to use. Many services support requesting multiple limit increases for the same service through one support case. After creating your first request, choose Add another request and then choose a new limit type or Region.
This is from the amazon ec2 FAQ :
Q: How quickly can I scale my capacity both up and down?
Amazon EC2 provides a truly elastic computing environment. Amazon EC2 enables you to increase or decrease capacity within minutes, not hours or days. You can commission one, hundreds or even thousands of server instances simultaneously. When you need more instances, you simply call RunInstances, and Amazon EC2 will typically set up your new instances in a matter of minutes. Of course, because this is all controlled with web service APIs, your application can automatically scale itself up and down depending on its needs.
Now again as per the same FAQ, I am only allowed to launch 20 instances per region. They said, I have to fill in a request form if I need more than 20 instances. So, in effect, I cant spin up more than 20 programmatically ?
What am I missing here ? how can we launch 100 instances let alone thousands. Sorry if this is the wrong place for such a question.
You cannot launch instances beyond the instance limit. You need to make a request to increase the instance limit. This is a safety feature so that:
A wild loop in your SDK/API script does not launch instances continuously
A malicious user does not launch a large number of instances
A hacker gets access to your account and launches a large number of instances
An incorrectly configured autoscaling group launches huge number of instances
If you require more than your instance limit, you need to submit a request to AWS. See: Amazon EC2 Service Limits. AWS will review your request and approve it.
You are missing the fact that limit increase requests are very easy to make and are almost always granted with no questions asked within a day or two.
To request a limit increase:
Open the AWS Support Center page, sign in if necessary, and choose Create Case.
For Regarding, choose Service Limit Increase.
Complete Limit Type, Use Case Description, and Contact method. If this request is urgent, choose Phone as the method of contact instead of Web.
Choose Submit.
AWS faqs provides a clear answer
You are limited to running up to a total of 20 On-Demand instances across the instance family, purchasing 20 Reserved Instances, and requesting Spot Instances per your dynamic Spot limit per region. New AWS accounts may start with limits that are lower than the limits described here. Certain instance types are further limited per region as follows
For Spot instance limits AWS states
The usual Amazon EC2 limits apply to instances launched by a Spot Fleet, such as Spot request price limits, instance limits, and volume limits. In addition, the following limits apply:
The number of active Spot Fleets per region: 1,000
The number of launch specifications per fleet: 50
The size of the user data in a launch specification: 16 KB
The target capacity per Spot Fleet: 3,000
The target capacity across all Spot Fleets in a region: 5,000
A Spot Fleet request can't span regions.
A Spot Fleet request can't span different subnets from the same Availability Zone.
These limits protect you from a hacker attack, stolen API keys, ETC. If you want to increase these limits, you need to send a form to AWS support team: AWS Support Center
I am trying to launch 210 instances of type p2.xlarge. Earlier I am hitting instance limit which I have increased now to 300 but now I am getting 'Client.VolumeLimitExceeded: Volume limit exceeded' error. Can you please help to resolve this issue? Any one knows the
What is Volume limit?
What should I request to increase inorder to run 210 instance (p2.xlarge) and aviod this error.
Your error means: Client.VolumeLimitExceeded: The limit on the number of EBS volumes or total storage was exceeded. Decrease usage or request an increase in your limits.
The AWS Limits page for EBS lists the default limit being 5,000 EBS volumes and 10,000 EBS snapshots. Total storage limit is 20 TB per type (gp2, io12, st1, sc1). Make sure that this is not your issue.
Amazon Elastic Block Store (Amazon EBS) Limits
To request an increase for EBS go to Volume List Increase Request. On the same page your can change the Limit Type for other limit increases.
I would open a support case with Amazon support and ask them to review your requirements to make sure that all your limits are managed for this usage case instead of hitting one limit after the other. Amazon will definitely help you.
The default EBS limits are: Amazon Elastic Block Store (Amazon EBS) Limits
It is the number of EBS volumes an account can use. You have a bigger problem if you are launching 210 p2.xlarge instances. You will hit various resource limits. You may need to request increase in limits for those resources.
Delete unattached/unused EBS volumes in your account
Check your EBS limits in: Amazon EC2 Service Limits
Calculate the number of volumes you will be using for each instance (Check your AMI)
Request for more EBS volume limit.
Is there any changes for "traffic" when using basic version of EC2 instance, by basic I mean:
750 hours per month of Linux, RHEL, or SLES t2.micro instance usage
Traffic: If we setup a server and there are some hits on my server then is there any charge for this setup. I am not using ELB, just EC2 instance with a server on it.
The full pricing for On-Demand Amazon EC2 instances can be found at: https://aws.amazon.com/ec2/pricing/on-demand/
The AWS Free Usage Tier gives 750 hours per month of a t2.micro instance. This means you could run one instance for a full month, or two instances for half a month. Simply stop the instance(s) to stop the charges.
You can have this free usage tier for a Linux AND a Windows instance.
However, please note that there are additional charges that also apply:
Data Transfer: This is charged for data leaving the AWS Region going to the Internet. The free usage tier includes "15 GB of bandwidth out aggregated across all AWS services" in the first 12 months. The EC2 pricing page also says that the first 1 GB/month is free, but I'm not sure if they overlap.
EBS Volume storage: Elastic Block Store (EBS) runs the disks attached to your instance. The free usage tier includes "30 GB of Amazon Elastic Block Storage in any combination of General Purpose (SSD) or Magnetic, plus 2 million I/Os (with EBS Magnetic) and 1 GB of snapshot storage", so you will be charged if your disk storage exceeds this (which is likely if you run both a Windows and a Linux instance). This storage charge continues to apply when an instance is Stopped, but not when an instance is Terminated.
Bottom line: Stop or turn off things when you don't need them. You can also activate a billing alert to warn you when you have been charged some actual money.
Yes, there are varying charges for traffic into and out of your EC2 instance.
in very rough numbers, if you budgeted $0.01 per GB of traffic, you would come in under that, but the complete breakdown is here:
https://aws.amazon.com/ec2/pricing/on-demand/