News for hackers. Stuff that matters.
Re:AWS status updates not working due to S3 by BrailleHunting on Tuesday February 28, 2017 @02:58PM (#13757273)
This is a problem of "monoculture" dependencies and failure to implement HA by using multiple services. All Github releases are down, atom downloads are down and so on. Companies, including Amazon, should be using other CDNs for HA purposes, even if NIH.

It's a similar mistake of making DNS a dependency for monitoring/control infrastructure when DNS is down.

Re:AWS status updates not working due to S3 by ghaff on Tuesday February 28, 2017 @03:16PM (#13757435)
Assuming that it actually makes business sense to do so. There are certainly cases where you can make a perfectly rational business decision to depend on someone else's services and you're OK with your uptime not being any better than their uptime.
Re:AWS status updates not working due to S3 by snuxoll on Tuesday February 28, 2017 @03:50PM (#13757680)
> It's a similar mistake of making DNS a dependency for monitoring/control infrastructure when DNS is down.

This one is relatively easy to "fix" at least, it's nothing having multiple DNS providers for public records can't handle as well as ensuring redundancy for your internal DNS services. Bonus points if you run your own recursive resolver so you aren't dependent on some other party not screwing up somehow.