How to Troubleshoot AWS M8G Large Instance Selection Errors

Select Language:

If you’re having trouble launching a m8g.large instance into your chosen Availability Zone (us-east-1e), chances are it’s because this specific instance type isn’t available in that zone, even though it’s available somewhere else within the region.

Here’s what you can do to fix this problem:

First, remember that different Availability Zones in the same region might not all support the same instance types. So, if it’s available in us-east-1a but not in us-east-1e, you’ll need to pick a different zone.

Second, certain Amazon services like RDS Aurora don’t support every instance type. For Aurora, only specific classes, mainly r-type (memory-optimized) instances, are supported, and m8g.large isn’t one of them.

If you’re working with EC2 or another service that supports m8g instances, here are your options:

Switch to a different Availability Zone within us-east-1 that supports the m8g.large.
Choose a similar, compatible instance type that is available in your desired zone.
Use the AWS Command Line Interface (CLI) to check which instance types are available in specific Availability Zones.

To find out what instance types are available in a particular zone, run this command:

bash
aws ec2 describe-instance-type-offerings –location-type “availability-zone” –filters Name=location,Values=us-east-1e –region us-east-1 –query “InstanceTypeOfferings[*].[InstanceType]” –output text | sort

Also, a quick note: in your original question, you mentioned “m2.medium,” but that doesn’t exist in AWS. You probably meant “t2.medium,” which is a common instance type.

If you want more details or run into other issues, check out these helpful links:

By following these steps, you should be able to find the right instance type in the correct zone and get your project back on track.