Launch instance - Can't do "not specify availabillity zone" in the console.

1

When I try to launch p2.xlarge, I sometimes get:

We currently do not have sufficient p2.xlarge capacity in the Availability Zone you requested (us-east-1b). Our system will be working on provisioning additional capacity. You can currently get p2.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a, us-east-1c, us-east-1d, us-east-1e.

However, there's no way in the console to remove the availability zone, just to change it, and then I need to try one by one... How to solve it?

asked a year ago199 views
1 Answer
0

The availability zone is determined by the subnet in which you place the instance. Visit the VPC console and select the Subnets view. Make sure you're looking at the correct VPC, then note all the subnets available in that VPC and which availability zone the subnet corresponds to. Make a note of each subnet and its zone. Now go back to EC2 to launch the instance, and choose a subnet for the availability zone that has the instance type that you need. You may need to try a few subnets/zones before you find one that has capacity.

profile picture
EXPERT
bwhaley
answered a year ago
  • But this is exactly the problem. It's super inefficient.

    1. Why is there no way to simply NOT choosing the AZ, like the error messages says, and let AWS decide the AZ in which there is available capacity? What's the point in doing it manually over and over again for each of the availability zones?

    2. Why Amazon doesn't make a dashboard in which we can see in which AZ there is NO capacity a t the moment for a specific instance type? It's one hour for an engineer...

  • That sounds like a feature request, not a question.

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