A user has launched an EBS backed EC2 instance in the US-East-1a region. The user stopped the instance and
started it back after 20 days. AWS throws up an ‘InsufficientInstanceCapacity’ error. What can be the possible
reason for this?
A.
AWS does not have sufficient capacity in that availability zone
B.
AWS zone mapping is changed for that user account
C.
There is some issue with the host capacity on which the instance is launched
D.
The user account has reached the maximum EC2 instance limit
Explanation:
When the user gets an ‘InsufficientInstanceCapacity’ error while launching or starting an EC2 instance, it
means that AWS does not currently have enough available capacity to service the user request. If the user is
requesting a large number of instances, there might not be enough server capacity to host them. The user can
either try again later, by specifying a smaller number of instances or changing the availability zone if launching
a fresh instance.
A
0
0
That new. A http://shlomoswidler.com/2009/10/avoiding-ec2-insufficientinstancecapaci.html
0
0
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-capacity.html
A
0
0
a
0
0
Error: InsufficientInstanceCapacity
If you get an InsufficientInstanceCapacity error when you try to launch an instance, AWS does not currently have enough available capacity to service your request. Try the following:
Wait a few minutes and then submit your request again; capacity can shift frequently.
Submit a new request with a reduced number of instances. For example, if you’re making a single request to launch 15 instances, try making 3 requests for 5 instances, or 15 requests for 1 instance instead.
Submit a new request without specifying an Availability Zone.
Submit a new request using a different instance type (which you can resize at a later stage). For more information, see Resizing Your Instance.
Try purchasing Reserved Instances. Reserved Instances are a long-term capacity reservation. For more information, see: Amazon EC2 Reserved Instances.
0
0
a
0
0
A
0
0