6 ms·
I dunno how else to put it. Having EVERYTHING on AWS is a national security threat. This isn't good, and someone who can do something about it needs to.
by dmalvarado 4y ago
I dunno how else to put it. Having EVERYTHING on AWS is a national security threat.
This isn't good, and someone who can do something about it needs to.
- harryh 4y agoThere is no "someone" who could do anything about this.
- gtirloni 4y agoGood thing we don't have EVERYTHING on AWS, so no threat detected.
- smt88 4y agoOur own applications are hosted on Azure, but we had an outage today anyway. It was because apparently Netlify and Auth0 use AWS and went down, which took down our static sites and our authentication. The nature of our business means it wasn't a big deal, but I could imagine lots of people were in the same boat.
- outworlder 4y agoYeah, let's place everything in large colos instead. Those never fail, right?
- Nextgrid 4y agoBut the colos aren't usually managed by a single control plane controlled by a single company, so while they can all fail, they will generally do so independently.
- scubbo 4y agoHaving _everything_ on a single AZ of AWS is, indeed, a problem. Having everything well-architected on AWS is...well, it's a problem for reasons of monopoly and cost, but it's not a problem for availability.
- Nextgrid 4y agoCertain "global" AWS services depend on a specific region (us-east-1 if I recall right) so if that goes down you could be in trouble.