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
Trigger an eventbridge event when an ecr image is pulled. For my specific use case when an archived image is pulled, but the more general event would be preferable.
Which service(s) is this request for?
ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
While updating ecr lifecycle policies to migrate images to an archived states based on sinceImagePulled I wanted to introduce a lambda that could initiate an auto-restore if an archived image had a pull request issued.
This would be an auto remediation that would reduce the time to recovery from a prematurely archived to less than a minute (not counting how ever long the restore takes).
Are you currently working around this issue?
Probably just won't have have the failsafe in place. I imagine there are ecs events that could be hooked into when a service fails to launch a task and could check the specific reason for the specific error message, but that tooling would need to at least partially sprawl across multi-regions/accounts and didn't seem worth the complexity
Additional context
nope
Attachments
n/a
Community Note
Tell us about your request
Trigger an eventbridge event when an ecr image is pulled. For my specific use case when an archived image is pulled, but the more general event would be preferable.
Which service(s) is this request for?
ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
While updating ecr lifecycle policies to migrate images to an archived states based on
sinceImagePulledI wanted to introduce a lambda that could initiate an auto-restore if an archived image had a pull request issued.This would be an auto remediation that would reduce the time to recovery from a prematurely archived to less than a minute (not counting how ever long the restore takes).
Are you currently working around this issue?
Probably just won't have have the failsafe in place. I imagine there are ecs events that could be hooked into when a service fails to launch a task and could check the specific reason for the specific error message, but that tooling would need to at least partially sprawl across multi-regions/accounts and didn't seem worth the complexity
Additional context
nope
Attachments
n/a