You only get slashed if you run malicious custom code, or if you run the same key on two machines at the same time.
The latter is a mistake that's very easy to make if you try to build auto-failover.
So don't build it. My validators operate with 'screen' and shell scripts. If I need to do anything (3-4 times a year), I do it manually.
- machine dies at 4am, what happens? do you manually restart process when you wake up? does this down time cause slashing?
- what mechanism prevents you from running 2 identical validators by accident?
If you have monitoring that alerts you for updates and when your node is unresponsive and can respond to downtime requiting intervention within a day or two you should still end up ETH-positive.
There is also a penalty that kicks in if many validators fail at the same time resulting in over 1/3 of the network not being available. In that case penalties are also increased significantly. So if over 1/3 of the network were to be run in AWS those validators would risk heavy penalties if the region were to suffer some downtime.
I'm curious how the big crypto companies are managing these large fleets of servers without doing some form of Devops? Looking at the docs there's a stack that needs to be deployed and maintained:
https://ethereum.org/en/developers/docs/nodes-and-clients/ru...