I would report this to AWS but for the life of me I can't figure out how to without having to pay for a support subscription (that I don't need).
Personally I've found a (not nice) workaround for now, but this should probably be fixed.
ami-084b0ab87791797ba
aws ec2 describe-images --region eu-west-1 --image-ids ami-084b0ab87791797ba
{
"Images": [
{
"Architecture": "x86_64",
"CreationDate": "2023-04-21T19:43:03.000Z",
"ImageId": "ami-084b0ab87791797ba",
"ImageLocation": "aws-marketplace/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20230325-84dfee58-b88e-45ac-b133-db810fba9d60",
"ImageType": "machine",
"Public": true,
"OwnerId": "679593333241",
"PlatformDetails": "Linux/UNIX",
"UsageOperation": "RunInstances",
"ProductCodes": [
{
"ProductCodeId": "7v6zoqj7fqa0yxobp2glr6kps",
"ProductCodeType": "marketplace"
}
],
"State": "available",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": true,
"SnapshotId": "snap-0e31fd25610ed18db",
"VolumeSize": 8,
"VolumeType": "gp2",
"Encrypted": false
}
},
{
"DeviceName": "/dev/sdb",
"VirtualName": "ephemeral0"
},
{
"DeviceName": "/dev/sdc",
"VirtualName": "ephemeral1"
}
],
"Description": "Canonical, Ubuntu, 22.04 LTS, amd64 jammy image build on 2023-03-25",
"EnaSupport": true,
"Hypervisor": "xen",
"ImageOwnerAlias": "aws-marketplace",
"Name": "ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20230325-84dfee58-b88e-45ac-b133-db810fba9d60",
"RootDeviceName": "/dev/sda1",
"RootDeviceType": "ebs",
"SriovNetSupport": "simple",
"VirtualizationType": "hvm",
"BootMode": "legacy-bios",
"DeprecationTime": "2025-04-21T19:43:03.000Z"
}
]
}
Looks like an Ubuntu 22.04 image right? Wrong.
Search for ami-084b0ab87791797ba in AWS market place and its:
Causal AI Platform (CAP) for AI MC
By: DeepCyber Latest Version: 3.1
The only give away in the API response (same via boto3 btw) is the product-code.
Given that Ubuntu server is free and this image isn't.... that seems a little sneaky at best to me as any scripts selecting the latest Ubuntu image using the API will likely get stung. Luckily you have to subscribe to it first to be able to use so unlikely to do any real harm I suppose.
Anyone know how to get this reported/ corrected?
Thank you for reporting this issue. We have an internal ticket open to investigate this.