Amazon S3 Service Disruption Explained
I recently was given a link to the official explanation from Amazon of the issues they had February 28th, 2017. First, let me say I love the transparency. If you expect me to trust you with running my business infrastructure, then I expect honesty from you. Hats off to Amazon Web Services. Well done.
The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected. At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that is used by the S3 billing process. Unfortunately, one of the inputs to the command was entered incorrectly and a larger?set of servers was removed than intended.
Click Here for the ?Full link to?Amazon S3 Service Disruption Explained.
Amazon Web Services won’t be the first nor the last company to get affected by human error. Its refreshing to see a company own up to it. Amazon S3 Service Disruption Explained – This was the right thing to do.
My newest presentation V202. The Cloud Landscape Today will be given at the Big Data Summit this May 15-17 ?in New York City and is a must see if you are thinking of migrating to the cloud. You can also download my Dirty Little Secrets of the Cloud presentation and used the cloud provider checklist in the back to help you make the right decision.
Let me say it again. I love the transparency. If you expect me to trust you with running my business infrastructure, then I expect honesty from you. Hats off to Amazon Web Services. Well done for taking the time to fully explain the Amazon S3 Service Disruption of February 28th, 2017.
Corey & Associates – Technology & Business Advisors
My Blog: http://michaelcorey.com/
My Personal Twitter Account:?Michael_Corey
Columnist for the Big Data Quarterly. <Click Here to Subscribe Big Data Quarterly>