View Issue Details

IDProjectCategoryView StatusLast Update
0018295CentOS-7Cloud-Imagespublic2021-09-01 15:42
Reporterukarad Assigned To 
Status newResolutionopen 
Product Version7.9.2009 
Summary0018295: Cannot use CentOS7 legacy AWS AMI to start an AWS m6i instance

A few years back, to run CentOS instances in AWS, we picked the "CentOS-7 x86_64" AMI from and running them successfully on the AWS m5 instances. Recently, AWS released a new instance type m6i and our instances failed to be upgraded to m6i. Digging into the issue, we found out that the base CentOS AMI we picked is currently listed under "Legacy CentOS Public Images" on the with the product code "aw0evgkw8e5c1q413zgy5pjce" and cannot be used to start on an m6i instance. The CentOS7 AMI listed under "Official and current CentOS Public Images" works fine on m6i instance.

We are wondering what is the difference between both these AMIs that for one, m6i cannot be used? To provide further details, our instances are all upgraded for ENA support and should be able to run on m6i instance if not for a policy set for the base AMI. Further, we checked our instances m6i support using NitroInstanceChecks script found at and that looks good.
OK NVMe Module is installed and available on your instance
OK ENA Module with version 2.0.3K is installed and available on your instance
OK fstab file looks fine and does not contain any device names.
Is there anyway that the Legacy CentOS Public Images can be enabled for AWS m6i instance support?
Steps To Reproduce1. Go to and scroll down to find the "Legacy CentOS Public Images" section
2. Pick the "CentOS-7 x86_64" (Direct link: and try to start an m6i instance and that shows disabled.
TagsAmazon, aws, centos7, m6i


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-09-01 15:42 ukarad New Issue
2021-09-01 15:42 ukarad Tag Attached: Amazon
2021-09-01 15:42 ukarad Tag Attached: aws
2021-09-01 15:42 ukarad Tag Attached: centos7
2021-09-01 15:42 ukarad Tag Attached: m6i