3 ms·
So I've considered this before, and I know it is coming from a good place. It seems great for the good times. At Clarify.io we use immutable infrastructure and
by grhmc 11y ago
So I've considered this before, and I know it is coming from a good place. It seems great for the good times. At Clarify.io we use immutable infrastructure and we don't log in to boxes. Except when there are problems. And there are problems. Always.
You don't want to have to fight your way in in the middle of a disaster.
At Clarify.io we've considered having an on-login event fire when an admin uses SSH to log in to the box. This would schedule the server for termination within 24 hours. This gets you best of all worlds:
- Gives tools to debug and restore service when there is a failure
- Forces admins to not depend on SSH to bring a system up
- Replaces servers when they are potentially drifting
- Encourages a "cattle" mentality about the servers
- aalbertson 11y agoI really like this idea. Would be keen to see what your orchestration code looks like to handle that.
- grhmc 11y agoWe already use JanitorMonkey. It would likely involve tagging the instance in AWS with a tainted tag, and adding code to JanitorMonkey to do the normal mark-and-sweep.
- aalbertson 11y agoThat's awesome! I don't know how I've missed JanitorMonkey amongst their tools, but that looks great. Definitely giving it a whirl.