pfrields reported a new issue against the project: `atomic-wg` that you are following:
AWS supports arbitrary tagging for images (user can set a key:value pair and the keys
don't seem to be restricted). Currently AFAICT from looking at the corpus of uploaded
snapshots we are not using this feature at all. A few random AMIs seem to have a
"name" key with a value that looks a lot like the released filename or ISO
volume name, but that's just a handful (under a dozen out of almost 4,000
We should be using tags to make it easier to sort and group these images to determine
usage, reap them, etc. For example:
origin: atomic, base, etc.
release: 27, 28, etc.
timing: prerelease, release
phase: Beta, GA
These are just strawmen. Other tags are fine. The key is to be able to effectively sort
and discover information about classes of images, which is virtually impossible (at least
through the AWS console) at the moment given they aren't delineated in any way. This
seems like an "easyfix" from a code perspective, it's probably more work to
decide on tagging itself.
To reply, visit the link below or just reply to this email