3 ms·
This is a testament to why you would want to use AWS virtual instances and never have "a server" - point your domain at a new instance should one machine get or
by samstave 15y ago
This is a testament to why you would want to use AWS virtual instances and never have "a server" - point your domain at a new instance should one machine get ordered off by the FBI.
- carguy1983 15y agoWow, you place an awful lot of faith in amazon.
- samstave 15y agoNot really actually, I just mean having a discrete server that can be "seized" is not a particularly robust solution.
- carguy1983 15y ago... and what do you think an Amazon slice is? It sits on a physical machine that can be identified, located, and handed over by Amazon given a lawful request, all without the site operators knowing. You think they give a fuck about the other 4 slices on your server? No. They don't. In fact it says so right in their SLA.
- samstave 15y agoI used the word ROBUST If you are trying to defy the FBI, and 100% of your site architecture resides within Amazon's infrastructure you are not robust.
- soult 15y agoGood idea. "The cloud" worked real wonders for Wikileaks.
- guccimane 15y agoFlouting law enforcement does not strike me as a good design goal. If the law wants you to stop doing something, they will make sure you stop.
- samstave 15y agoLaw enforcement, failed hard drive, link outage, whatever... They are all the same == Downtime. My point is that if you have a "server" that can be seized, you have not designed a robust system. Imagine the FBI trying to seize Google or Amazon or Facebook (well, a lot easier in the case of facebook only because they have so few datacenters by comparison.)