2 ms·
Sadly, you'll still encounter pages in the middle of the night (well, if you implement the monitoring) when AWS services fail and you need to write up a support
by falcolas 8y ago
Sadly, you'll still encounter pages in the middle of the night (well, if you implement the monitoring) when AWS services fail and you need to write up a support ticket.
Granted, they're usually already aware of it, but it can still take tens of minutes to hours to resolve - time during which you are down.
- scarface74 8y agoIn the case of the parent poster - using AWS to manage load balancers and database failovers, how often would a failure be noticed by the end user? Yes, I know what happens when client apps/servers cache the DNS entry too long and don’t notice when a failover takes place - been there done that. And the quickest way to recover from a failure of servers that don’t store state is just to let autoscaling kill it and bring up another instance based on an AMI/startup scripts. I’m ruthless about not having servers as pets for anything that we have to manage ourselves. I tell our Devops guy that it is completely useless to keep an inventory of server names, IP addresses, etc. for anything that I’m responsible for.