New backport AMI jumped ahead
Just a FYI for people who use filters to select Buster AMIs.
We use the following to pick the AMI:
aws ec2 describe-images --filters \
Then we sort this list by CreationDate and pick the last one, meaning
we always use the latest image, which is released roughly every month.
This worked well - so far.
I just noticed that my dev environment was running on a fancy 5.10
kernel. After some investigation I found that on 29 March there were
*two* AMI released: one regular one, plus a backport one:
Because the glob pattern for the Name matches both, and the backport
one was released 10 minutes later, this was picked....
I have now updated the glob to "debian-10-amd64-*" so that we pick the
non-backported AMI again.
Trust & Identity Service Operations Manager