buildkite
Question: can lifecycled process requests for other instances?
One use case for lifecycled is that you run it on all EC2 instances, and when an instance terminates, you run the action on the instance that is terminating.
Another use case is to run those actions on a single/central management instance, rather than the instance that is terminating. There might be a variety of reasons for this, such as reliability, management access or permissions constraints in the env.
With a review of the go code, it seems lifecycled is restricting actions to the instance it is running on, is that true?
With a review of the go code, it seems lifecycled is restricting actions to the instance it is running on, is that true?
Yep, each instance will only act on termination events that are targeting its own instance ID. The difficulty with running it centrally is that you'd need another way to initiate the shutdown script on the host that is being terminated, which I believe would increase complexity a lot 🤔
The difficulty with running it centrally is that you'd need another way to initiate the shutdown script on the host that is being terminated, which I believe would increase complexity a lot 🤔
For some use cases, the actions taken are with a central system and can be run from a single instance responsible for running a tool like lifecycled.
@itsdalmo would making the filter optional be enough to make this a reality?