bug: Amazon Linux 2023 EC2 Image not tagged to all the correct AMI IDs #10764
Labels
area: integration/cdk
Issues related to AWS Cloud Development Kit
aws:cloudformation
AWS CloudFormation
aws:ec2
Amazon Elastic Compute Cloud
aws:ssm
AWS Systems Manager
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
When spinning up a EC2 pointing at
MachineImage.latestAmazonLinux2023()
, LocalStack will clone the Amazon Linux 2023 image and tag it with theami-024f768332f0
AMI, while the stack resolves the desired AMI ID toami-0e58172bedd62916b
causing the error ofExpected Behavior
The AMI ID that the Amazon Linux 2023 image is tagged with should also be what's stored in the SSM Parameter for
/aws/service/ami-amazon-linux-latest/al2023-ami-kernel-6.1-x86_64
, or an image matching that should also be downloaded and tagged correctly. Either way, the Stack should be able to resolve the correct AMI ID and deployHow are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Environment
Anything else?
I've reproduced the issue here: https://github.com/Garethp/localstack-bugs/tree/ec2-latestAmazonLinux2023
If you clone down the branch
ec2-latestAmazonLinux2023
, run yarn install, and then ./start.sh you should see the issue in action.Additionally, if you run
awslocal ssm get-parameters-by-path --path /aws/service/ami-amazon-linux-latest
you can see that there might be other paths forAmazonLinux2023
to resolve to, but just callingMachineImage.amazonLinux2023()
will resolve the/aws/service/ami-amazon-linux-latest/al2023-ami-kernel-6.1-x86_64
SSM Parameters for it's AMINotes from @simonrw:
The text was updated successfully, but these errors were encountered: