Improve Image Lifecycle Policy Resource Selection

[sophiecosgrove]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
What do you want us to build?
Be able to specify either names of recipes or wild carded recipe versions within the resource selection of lifecycle policies. Additionally be able to tag output image resources in the distribution configuration, similar to how outputted AMIs are tagged currently.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

We are wanting to use lifecycle policies to manage resources created by EC2 Image Builder however we are unable to use either the tag or recipe selection option to attach them to resources.

The recipe selection takes in a full ARN, with no option to use a wildcard character, this means that we would have to update the lifecycle policy every time that the recipe is updated and changes version.

The second option is to specify tags which are present on the image resource, however there is currently no way to tag this resource besides a CLI command.

Are you currently working around this issue?
How are you currently solving this problem?
Manually tagging image resources and looking to replace this with a Lambda function.