aws_ec2: Parameter cpu_type ignored when calling ec2.MachineImage.latest_amazon_linux2023()

[jedreky]

Describe the bug

I am using AWS CDK in Python. I want to get the latest Amazon Linux AMI for either x86 or arm architecture, to do this I call:

ec2.MachineImage.latest_amazon_linux2023(cpu_type=ec2.AmazonLinuxCpuType.X86_64).ssm_parameter_name()
ec2.MachineImage.latest_amazon_linux2023(cpu_type=ec2.AmazonLinuxCpuType.ARM_64).ssm_parameter_name()

Expected Behavior

I would expect to get two different outputs.

Current Behavior

In both cases I get:

'/aws/service/ami-amazon-linux-latest/al2023-ami-kernel-default-x86_64'

Reproduction Steps

import aws_cdk.aws_ec2 as ec2
print(ec2.MachineImage.latest_amazon_linux2023(cpu_type=ec2.AmazonLinuxCpuType.X86_64).ssm_parameter_name())
print(ec2.MachineImage.latest_amazon_linux2023(cpu_type=ec2.AmazonLinuxCpuType.ARM_64).ssm_parameter_name())

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.109.0 (build 941dc16)

Framework Version

No response

Node.js Version

v20.5.1

OS

Linux

Language

Python

Language Version

3.11.1

Other information

No response

[khushail]

Hi @jedreky, thanks for reporting this

[lpizzinidev]

@jedreky
ssm_parameter_name is a static method and does not inherit the properties from the AmazonLinux2023ImageSsmParameter instantiated by latest_amazon_linux2023.

You should be able to retrieve the correct image with:

ec2.MachineImage.latest_amazon_linux2023(cpu_type=ec2.AmazonLinuxCpuType.ARM_64).get_image(scope).image_id

Or, if you want to use the static method:

ec2.AmazonLinux2023ImageSsmParameter.ssm_parameter_name(kernel=ec2.AmazonLinux2023Kernel.CDK_LATEST, cpu_type=ec2.AmazonLinuxCpuType.ARM_64)

[jedreky]

hey Luca, the first method works, thanks a lot :)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.