- Newest
- Most votes
- Most comments
Couple things to try:
- Check Service Quotas in the Console and ensure that you have a limit greater than 0 for the instance type.
- Make sure that the Architecture that you are specifying matches the instance. hpc7g.16xlarge The "g" in the instance type indicates it is a Graviton (64bit ARM) instance and not x86_64.
- Try launching with a default Amazon Linux AMI just to ensure that your custom image is not the issue.
If all else fails, contact AWS Support for assistance.
Hello,
Generally, you might receive such error in one of the following two issues:
- The specified instance type isn't supported in the requested Availability Zone. To check the availability of the instance types in specific Availability Zones, run the aws ec2 describe-instance-type-offerings command in the AWS CLI. Then, launch the instance in a supported Availability Zone.
For example:
$ aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=c5.2xlarge --region us-east-1
- The Amazon Machine Image (AMI) that's used to launch the instance doesn't support the selected instance type. Before you select the instance type or family, review the AMI descriptions in the AWS Marketplace. This issue commonly occurs when you use AWS Marketplace AMIs, and try to launch unsupported instances using the AWS CLI. When you launch instances from the Amazon EC2 console, unsupported instances are unavailable.
If you can provide more details mentioned below for the issue you are facing, it would be more helpful.
- Are you using AWS Console or CLI for launching the instance.
- Which AMI you are using to launch the instance. Is it Marketplace AMI. If it is a Marketplace AMI, then does it support the instance type you are using. You can check supported configuration on the AWS Marketplace product page.
- What exact and complete error message you are getting when sending RunInstances API call or launching instance.
Moreover, you can use the AWS Document here for troubleshooting EC2 instance launch failures.
Hello Tarun_S, I usually launch directly from the console. The CLI is outputting: aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=c5.2xlarge --region us-east-1 [cloudshell-user@ip-10-6-183-143 ~]$ aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=hpc7g.16xlarge --region us-east-1 { "InstanceTypeOfferings": [ { "InstanceType": "hpc7g.16xlarge", "LocationType": "availability-zone", "Location": "us-east-1c" } ] } I tried specifying choosing the available subnet for us-east-1c (instead of letting the console choose whichever it prefers as I usually do), but the launching initiation failed. I wish that re:Post allowed me to post screenshots but a copy of the logs reads: Instance launch failed Value (hpc7g.16xlarge) for parameter instanceType is invalid. 'hpc7g.16xlarge' is an unsupported instance type
Launch log Initializing requests Succeeded Creating security groups Succeeded Creating security group rules Succeeded Launch initiation Failed
Regarding the AMI, I built my own, which has worked in pretty much every Gv2 or Gv3 instance (e.g. r6g, r7g, t4 ) and it worked even with c7gn yesterday and earlier today. Thanks.
Relevant content
- Accepted Answerasked 10 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Maybe this is new as there's a 'Running On-Demand HPC instances' quota in the 'Service Quotas' tab. I won't know if this is the issue until they approve my request. NOTE: I've launched hundreds of instances with the AMI so, if there were some incompatibility issues, it'd be at the hpcg7g end.
Just keep in mind that AMIs either support x86_64 or ARM, not both with the same AMI.