Dec 2, 2010: Amazon cuts off WikiLeaks

"Amazon Web Services (AWS) rents computer infrastructure on a self-service basis. AWS does not pre-screen its customers, but it does have terms of service that must be followed. WikiLeaks was not following them."


Statement from Amazon Web Services:

"There have been reports that a government inquiry prompted us not to serve WikiLeaks any longer. That is inaccurate.

There have also been reports that it was prompted by massive DDOS attacks. That too is inaccurate. There were indeed large-scale DDOS attacks, but they were successfully defended against.

Amazon Web Services (AWS) rents computer infrastructure on a self-service basis. AWS does not pre-screen its customers, but it does have terms of service that must be followed. WikiLeaks was not following them. There were several parts they were violating. For example, our terms of service state that “you represent and warrant that you own or otherwise control all of the rights to the content… that use of the content you supply does not violate this policy and will not cause injury to any person or entity.” It’s clear that WikiLeaks doesn’t own or otherwise control all the rights to this classified content. Further, it is not credible that the extraordinary volume of 250,000 classified documents that WikiLeaks is publishing could have been carefully redacted in such a way as to ensure that they weren’t putting innocent people in jeopardy. Human rights organizations have in fact written to WikiLeaks asking them to exercise caution and not release the names or identities of human rights defenders who might be persecuted by their governments.

We’ve been running AWS for over four years and have hundreds of thousands of customers storing all kinds of data on AWS. Some of this data is controversial, and that’s perfectly fine. But, when companies or people go about securing and storing large quantities of data that isn’t rightfully theirs, and publishing this data without ensuring it won’t injure others, it’s a violation of our terms of service, and folks need to go operate elsewhere.

We look forward to continuing to serve our AWS customers and are excited about several new things we have coming your way in the next few months."



RELATED ARTICLESExplain
WikiLeaks
Reaction to WikiLeaks
Hysterical intimidatory campaign against WikiLeaks
Dec 2, 2010: Amazon cuts off WikiLeaks
Why did Amazon cut off WikiLeaks?
Can we trust private internet service providers to defend free speech?
Government and establishment media fear-mongering against WikiLeaks
18 Dec: Bank of America stops handling payments for Wikileaks
Dec 3, 2010: Library of Congress blocks access to Wikileaks website
Dec 4, 2010: PayPal Freezes WikiLeaks Account
Dec 6, 2010: MasterCard pulls plug on WikiLeaks payments
Dec 6, 2010: Swiss bank freezes Assange's legal defense fund
Intimidatory statements by US political figures
Jan 8, 2011: US judge orders Twitter to turn over Wikileaks accounts
People warned not to engage with the leaked material
Swedish charges against Julian Assange for sexual misconduct
Tom Flanagan: Julian Assange is a traitor and should be assassinated
US Air Force blocks media sites posting WikiLeaks (including NY Times)
Wikileaks has come under massive corporate attack to shut it down
Dec 16, 2010: Calls for restraint on prosecutions at Congress Hearing
Graph of this discussion
Enter the title of your article


Enter a short (max 500 characters) summation of your article
Enter the main body of your article
Lock
+Comments (0)
+Citations (1)
+About
Enter comment

Select article text to quote
welcome text

First name   Last name 

Email

Skip