- Newest
- Most votes
- Most comments
It is quite strange, it DOES supports M6id, according to Marketplace statement. And it also supports M5/C6i, so this AMI does not require any ephemeral storage.... So it seems there should not be any technical reason, not to support M6i....
Indeed, even in my environment, I could not select M6i at first startup.
The following documents seem to support M6i.
https://aws.amazon.com/marketplace/pp/prodview-q6d4utevggvnk?sr=0-1&ref_=beagle&applicationId=AWS-EC2-Console#pdp-overview
If there is no error when starting with AWS CLI, etc., it could be a bug in the management console, etc.
It may be a good idea to check the driver version using the method in the following document, just to be sure.
https://repost.aws/knowledge-center/migrate-to-gen6-ec2-instance
Relevant content
- asked 3 years ago
- asked a year ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
Do you get an error when starting with M6i in the AWS CLI?
NO. I can launch an instance with m6i.large, by ami-09b781df816feb92d. I am blocked, only at EC2 Management Console.