3 Big takeaways from Amazon’s latest cloud outage
In the wee hours of Sunday morning something went very wrong in an Amazon Web Services data center.
At 6 AM ET error rates for the company’s massive NoSQL database named DynamoDB began skyrocketing in AWS’s US-East Virginia region - the oldest and largest of its nine global regions. By 7:52 AM ET, AWS determined the cause of the problems: an issue with how the database manages metadata had gone awry, impacting the service’s partitions and tables.
Amazon Web Service's Health Dashboard shows the timeline of events from Sunday's outage, including the root cause.
To read this article in full or to leave a comment, please click here