I came across this when refreshing my memory on the Amazon server outage a few years back. I am still reading through it, but I thought I would post the links for others.
Amazon Server Outage, February 28, 2017:
https://www.emptywheel.net/2017/02/28/if-amazon-world-services-goes-down-do-the-cloud-services-aws-provides-the-intelligence-community-too/
"I want to know if, when Amazon’s Northern Virginia cloud services go down, whether the cloud services Amazon provides to the Intelligence Community goes down too. The IC cloud is supposed to be completely separate from AWS’ commercial services. But if things are going haywire generally in Northern Virginia, those problems may extend to Amazon’s (understood to be NoVA located) IC servers.
I raise that, in part, because of a point I made in these two posts about the new EO 12333 sharing rules Obama implemented in January. The data sharing envisioned can happen in one of three places: on NSA’s own servers, on the recipient agency’s own servers, or on the cloud."
https://www.emptywheel.net/2017/01/17/12333-info-sharing-working-thread/
https://www.emptywheel.net/2017/01/30/the-ironies-of-the-eo-12333-sharing-expansion-for-obama-and-trump/
"Hennessey’s assurances ring hollow. That’s true, first of all, because it is actually easier to change an EO — and EO 12333 specifically — than “a pen stroke.” We know that because John Yoo did just that, in authorizing Stellar Wind, when he eliminated restrictions on SIGINT sharing without amending EO 12333 at all. “An executive order cannot limit a President,” Yoo wrote in the 2001 memo authorizing Stellar Wind. “There is no constitutional requirement for a President to issue a new executive order whenever he wishes to depart from the terms of a previous executive order. Rather than violate an executive order, the President has instead modified or waived it.” And so it was that the NSA shared Stellar Wind data with CIA, in violation of the plain language of EO 12333 Section 2.3, until that sharing was constrained in 2004."