Clouds moved in over Seattle today as the Amazon S3 cloud-based storage service took some unexpected Zzzz's in an unexpected overnight outage.
So what's the problem?
Well, for starters, a host of startup companies (including Twitter) use the S3 service to host everything from images to Web content, and when the clouds get dark, so do many Web-based businesses dependent upon Amazon.
Of course, one astute S3 user in the Amazon Web Services Developer forum explained the need for diversification:
"If you rely on a single point of storage for mission critical data, well then, you've got bigger problems."
Nick Carr explains it's also important how the supplier responds, "in keep customers apprised of the situation and explaining precisely what went wrong and how the source of the problem is being addressed."
Apparently, Amazon has been keeping S3 users well informed.
But also Carr cited one user who observed: "A health monitor would be useful - something to show what amazon thinks the status of the services are and to post official information. Maybe even proactive alerts or something I could tie our other infrastructure notifications into so I could be proactive in alerting our downstream affected users."
Hmmmm...I do believe our Tivoli team provides some service management tools to stay on top of situations like that!
You can learn more by calling 1-877-426-3774 (please use priority code: 104CBW62).