
It has probably escaped no one that Amazon had several days of honest issues with its cloud hosting service last week, which took a large number of sites either fully or partly offline, counting sites like Reddit, Foursquare and Quora.
To say that this incident received a massive amount of media attention would be an understatement. The screenshot from a Google News search that we included above pretty much says it all (full last evening).
There’s an ancient TV news adage that goes, “if it bleeds, it leads.” We’re sure you’ve heard of it. This was the Internet equivalent of that.
This is one of the really huge downsides of running such a large operation online as Amazon does (or any really large web hosting company). When something goes down, it gets noticed, huge time. It becomes more than a nuisance, it becomes news.
That said, a huge outage like this one gives us all…
We’re sure that although this was a very frustrating incident for everyone involved, both Amazon and its AWS customers will come out of this with several valuable education learned. And we don’t reckon the lesson should be, “don’t trust cloud computing.” That would be very small sighted.
In fact, AWS will most likely become a better service because this. We’ve said it before, and we’ll say it again: Everyone will have downtime. It’s what you learn from it, what you do to minimize future downtime, that matters.
Some have by now been generous enough to share their experiences and advice.
If you use Amazon EC2 or some additional cloud computing platform, these articles are pretty much a must-read. Even if you’re on a more traditional hosting platform, we urge you check out the articles anyhow since much of what they discuss is relevant to all web services.
This was a post from the guys at Pingdom, a site monitoring service that makes sure you’re the initially to know when your site is down. Check it out for free.

From:
The Amazon EC2 outage left blood in the water, but now it’s time to learn from it