- 最新
- 最多得票
- 最多評論
If you run this command, it looks like one of AZs does not have that instance type.
aws ec2 describe-instance-type-offerings --filters Name=instance-type,Values=p4d.24xlarge --region us-west-2 --location-type availability-zone-id
{
"InstanceTypeOfferings": [
{
"InstanceType": "p4d.24xlarge",
"LocationType": "availability-zone-id",
"Location": "usw2-az3"
},
{
"InstanceType": "p4d.24xlarge",
"LocationType": "availability-zone-id",
"Location": "usw2-az1"
},
{
"InstanceType": "p4d.24xlarge",
"LocationType": "availability-zone-id",
"Location": "usw2-az2"
}
]
}
Greetings,
It seems that there is currently a capacity constraint for the p4d.24xlarge instance type in the "Oregon" (US-WEST-2) region with "gp2" volumes. This means that there are not enough available instances in the region with the specified storage type to meet your request.
To work around this issue, you may want to try using a different volume type for your EBS storage, such as "io1" or "st1". You can also try launching your instance in a different availability zone within the same region to see if capacity is available there.
If you continue to have difficulty launching a p4d.24xlarge instance in US-WEST-2, you may want to consider launching the instance in a different region where the instance type and storage type combination is available. Alternatively, you can try again later, as additional capacity may become available over time.
Please let me know if that answered your question
Thanks, I tried "io1" and "st1", but both of them showed the same error no sufficient capacity.
Did you find the right solution?
I also have the same issue, there is no capacity available for p4d.24xlarge instance-type in N. Virginia and Oregon regions. I have retried many times since 2 days ago but have had no luck. Is there any solution other than "try again later"?
相關內容
- 已提問 1 年前
- AWS 官方已更新 7 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thanks for the information, but I did not put preference on the AZ. I assume it should choose AZ automatically. But the instance still launch failed.
Specify a subnet that resides in one of those AZ above. You also may want to try with 'gp3' EBS volumes.
Thanks, but I tried US-WEST-2a, US-WEST-2b, US-WEST-2c (these are the options listed in the drop down list), same error. Also, I tried GP3, also showing same error.