View Issue Details

IDProjectCategoryView StatusLast Update
0016053CentOS-7Cloud-Imagespublic2019-05-28 20:53
Status newResolutionopen 
Product Version7.6.1810 
Target VersionFixed in Version 
Summary0016053: Latest AWS AMI for CentOS 7 does not support t3a/m5ad/r5ad instance types
DescriptionTesting e.g. with ami-02eac2c0129f6376b in us-east-1, one gets an "UnsupportedOperation" error from AWS when trying to create an instance with types t3a, m5ad or r5ad.

However, m5a and r5a work fine.

Full error:
An error occurred (UnsupportedOperation) when calling the RunInstances operation: The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems.
Steps To ReproduceYou can run this in us-east-1:
$ aws ec2 run-instances --image-id ami-02eac2c0129f6376b --count 1 --instance-type t3a.small

This is the latest CentOS 7 AMI (1901_01) for us-east-1, released on Jan 30th, 2019.
Full name: CentOS Linux 7 x86_64 HVM EBS ENA 1901_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-05713873c6794f575.4

Or do what's below; this will retrieve the latest CentOS 7 AMI for the given region and attempt to create a new instance with that AMI ID.
$ region=<your_chosen_region> # e.g. us-east-2, us-west-1, eu-west-2, etc.
$ aws ec2 run-instances --region $region --image-id $(aws ec2 describe-images --region $region --filters "Name=name,Values=CentOS Linux 7 x86_64 HVM EBS ENA*" "Name=virtualization-type,Values=hvm" "Name=ena-support,Values=true" --owners "679593333241" --query 'Images[*].[ImageId,CreationDate]' --output text | sort -k2 -r | head -n1 | awk '{print $1}') --count 1 --instance-type t3a.small
TagsAmazon, AMI, aws




2019-05-20 06:52

reporter   ~0034484

I suppose that this should "just" need the new instance types enabling in Centos's settings in the AWS marketplace:

(similar to )
(other varieties of "a" and "d" instance subtypes are already enabled, so should not have any particular testing/concern ?)


2019-05-23 05:38

reporter   ~0034504

I can verify that the AMI's contents do work with the T3a instance class.

Impatient as I am, I decided to clone the root volume to remove the product code, cut an AMI, and then launch that on a T3a instance. Worked like a charm. At this point, all that needs to be done is check a box to enable the instance types (or whatever that process is).


2019-05-28 08:10

reporter   ~0034525

This now appears to be resolved - I'm able to start t3a instance types directly without having to clone first.


2019-05-28 20:45

reporter   ~0034530

Agreed, this seems to work now for t3a/m5ad/r5ad instance types.

Issue History

Date Modified Username Field Change
2019-05-03 19:36 shubbeh New Issue
2019-05-03 19:37 shubbeh Tag Attached: Amazon
2019-05-03 19:40 shubbeh Tag Attached: AMI
2019-05-03 19:40 shubbeh Tag Attached: aws
2019-05-20 06:52 JamesJJ Note Added: 0034484
2019-05-23 05:38 SpencerD Note Added: 0034504
2019-05-28 08:10 dropkickimpact Note Added: 0034525
2019-05-28 20:45 shubbeh Note Added: 0034530
2019-05-28 20:53 shubbeh Issue cloned: 0016121