Instance fails to start due to "insufficient capacity" error

0

Over the past 2 days, I have been trying to start one of my instances, and repeatedly get "insufficient capacity" errors. I checked the support article regarding this, and none of the cases match my issue. I am not launching one, just trying to start an existing one. And as I mentioned, it has been a problem for over two days now (i.e. the "wait a few minutes" solution isn't working either). I also have tried starting this one when no other instance of mine is running, so I don't think it's a resource issue regarding me having too many instances running. It is only one particular instance having this problem. The others all start fine. I need this instance to be able to start so that I can perform tasks on it related to our customers. Is there any other solution besides the ones already given in the Troubleshooting section?

  • What instance type are you trying to use?

  • Also: What region and availability zone?

Ken
asked 2 years ago459 views
3 Answers
1

This error doesn't mean you might have too many resources running. It means AWS doesn't have enough capacity for that particular instance type in that particular availability zone. So as long as they don't have enough capacity for it in that availability zone, you won't be able to start it. You can ask AWS but I am guessing it's not that straightforward to add more capacity and those kind of things can take time. Since you have already tried starting it multiple times at different intervals, here's what I can suggest as a workaround.

  1. Change your instance type and try to start it again. Like I said, that instance type isn't available so you may have better luck changing the instance type and then try to start it again. Hopefully, the other instance type will have enough capacity. You can find a different instance type which has enough resources to support your workload. Take a look at the list: https://aws.amazon.com/ec2/instance-types/
  2. If you absolutely need to use the same instance type, then one workaround would be to create an AMI from your instance. And then re-launch the instance from your AMI in a different availability zone. There is no guarantee it would be work. But you can try your luck in a different availability zone.

NOTE: Before you do any of those, make sure to create a backup of your volume or an AMI of your instance to be on the safe side!

answered 2 years ago
0

Thanks tahatahir. I'll try changing the instance type. I see m1 isn't even listed as an instance type anymore, so maybe that could be my issue. Almost like an out-of-support thing. Ken

Ken
answered 2 years ago
  • m1 is a previous generation instance type. Should still be available. you would likely have to select previous generation instance types in the console. regardless, i would suggest perhaps trying to switch to one of the current generation instance types. you should be able to find one with enough resources for your use case

0

What region and availability zone? N. Virginia, and US East 1C.

What instance type are you trying to use? m1.small. It is a community AMI, as I needed an older Linux version with older system libraries (specifically, an older glibc version), and Amazon's AMIs are too "new".

Ken

Ken
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions