1 Answer
- Newest
- Most votes
- Most comments
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.
Relevant content
- Accepted Answerasked a year ago
- asked 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
But this is exactly the problem. It's super inefficient.
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?
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.