1 Answer
- Newest
- Most votes
- Most comments
1
It's in the error message - the m4.large instance type isn't available in all the AZs in your region. See https://repost.aws/knowledge-center/ec2-instance-type-not-supported-az-error
$ aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=m4.large --region us-west-1 --output table
-------------------------------------------------------
| DescribeInstanceTypeOfferings |
+-----------------------------------------------------+
|| InstanceTypeOfferings ||
|+--------------+--------------+---------------------+|
|| InstanceType | Location | LocationType ||
|+--------------+--------------+---------------------+|
|| m4.large | us-west-1c | availability-zone ||
|| m4.large | us-west-1b | availability-zone ||
|+--------------+--------------+---------------------+|
$
(note that the real-world locations of where AZs 1a, 1b & 1c map onto are different in your account compared to mine, which could be different again for other people's. But the main point is the instance type isn't available in that AZ, but is available in other AZs in that region)
Relevant content
- Accepted Answerasked 8 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
Thanks for getting back to me, m4.large looks to be available in us-west-1b for me
I'm in the UK so I'll look into this again tomorrow, but thanks for the response.
No worries. And that is very strange - my output was from CloudShell in the Sydney region, and I get the same with CloudShell running in London, and also CloudShell in us-west-1 itself. And the same again on a long-running EC2 in us-east-1.
I'll keep an eye on this question as I'm now interested to see how it goes.
I moved the subnet to the us-west-1a availability zone and Image Builder successfully launched a test instance. I'm not sure why my
aws ec2 describe-instance-type-offeringscame back as good for us-west-1b, but I'm glad its working now.Thanks again for your help