>Actually it is hard. Most of your peers and yourself may be familiar with the quirks, but that doesn't mean it isn't hard. AWS's docs are terrible. Others bein

>Actually it is hard. Most of your peers and yourself may be familiar with the quirks, but that doesn't mean it isn't hard. AWS's docs are terrible. Others being worse does't change that fact. I think you've confused what "facts" are... Doesn't matter. I guess some people are just destined to remain rack 'n stack sysadmins. Fine, more money and less competition for jobs then. >As for rock solid colo docs- there is this thing called Google. And in fact you barely need that. It's real easy to set up. I think you misunderstood my point. I know there are a thousand-and-one guides for setting up Nagios and Postfix and sticking HAProxy in front of it, but my point was that no amount of documentation can abstract away the actual pain points of dealing with co-los, including their owners, staff, and all the fun little problems that crop up with dealing with them. For when it actually matters beyond a dollar value, I trust AWS engineers a lot more than I do HPE/Equinix etc...