View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0018295||CentOS-7||Cloud-Images||public||2021-09-01 15:42||2021-09-01 15:42|
|Summary||0018295: 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 https://wiki.centos.org/Cloud/AWS 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 https://wiki.centos.org/Cloud/AWS 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 https://github.com/awslabs/aws-support-tools/tree/master/EC2/NitroInstanceChecks 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 Reproduce||1. Go to https://wiki.centos.org/Cloud/AWS and scroll down to find the "Legacy CentOS Public Images" section|
2. Pick the "CentOS-7 x86_64" (Direct link: https://aws.amazon.com/marketplace/pp/B00O7WM7QW) and try to start an m6i instance and that shows disabled.
|Tags||Amazon, aws, centos7, m6i|