http://gigaom.com/2013/03/15/by-the-numbers-how-google-compute-engine-stacks-up-to-amazon-ec2/ some interesting piece of data comparing AWS and GCE (google compute engine, i.e IAAS offering from google)
http://gigaom.com/2013/03/15/by-the-numbers-how-google-compute-engine-stacks-up-to-amazon-ec2/ some interesting piece of data comparing AWS and GCE (google compute engine, i.e IAAS offering from google)
http://pastebin.com/UW7iT5fj Linode VM hosting service was hacked. ~3000 Bitcoins were stolen
http://pastebin.com/UW7iT5fj Linode VM hosting service was hacked. ~3000 Bitcoins were stolen
http://aws.amazon.com/message/65648/ Postmortem for the April-2011 EC2/EBS outage. It looks like a human errors plus unfortunate cascade of events lead to a requests storm that brought down EBS storage. Also, it appears that Amazon mis-estimated spare storage capacity needed for recovery from such events.
http://www.slideshare.net/adrianco/netflix-in-the-cloud-2011 Slides from Adrian Cockcorft, Netflix director of cloud systems about current state [for 2011] of Netflix’s AWS-based architecture
http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html Notes from netflix tech blog about some key points of their EC2-based infrastructure design. Note that netflix is not affected by the current EBS problems in AWS US-EAST region. Their key point seems to be to equally split your infrastructure between 3 AZs (availability zones) and run at ~30% capacity, so if 2 AZs fail (as we have now) you would still running in one AZ @ 90%
http://ec2disabled.com/ The subj. looks really bad!
http://justinsb.posterous.com/aws-down-why-the-sky-is-falling A blog post explaining nature of the current Amazon AWS outage. The deal is that several so-called availability zones (AZ) failed simultaneously in amazon US-EAST region, even though amazon’s FAQ describe such event to be unlikely. Many interesting comments – read them!
http://code.mixpanel.com/amazon-vs-rackspace/ Notes about reasons why Mixpanel moves out of Rackspace cloud to EC2