Genuine questions, I don't know if this is the case or not.
I guess my point is the project should be providing a clear path that doesn't involve AWS instead of just stopping short.
tl;dr: Amazon prioritizes patching really well, fixing real issues first
Do you want to know if you are patched? Ok, well are you running the latest version? If so, you have all the available patches.
Most of the reason we need VM on a "traditional" OS is to handle the fact that they have a very broad configuration space and their software composition can be - and often is - pretty arbitrary (incorporating stuff from a ton of sources / vendors and those versions can move independently).
But that's not how you're supposed to use a container OS.
If you do "extra work" to discover vulnerabilities in "latest", you are not really doing the job of a system owner (whose job is mostly to apply latest patches from upstream in a timely fashion), you are doing the work of a security researcher.
It’s been around longer than Bottlerocket
I wish the Bottlerocket team would do 1 of 2 things. Either own up that this is just an AWS project, or start to solve for things like this and actually be a product that "runs in the cloud or in your datacenter" as they suggest on their website.
[1] https://bottlerocket.dev/en/faq/#4_2