Amazon Web Services (AWS) experienced a significant, day-long outage in its US-EAST-1 region, stemming from a race condition in DynamoDB's automated DNS management system that left an empty DNS record. This initial fault cascaded, impacting EC2 instance launches, network configurations, and dependent services like Lambda and ECS, disrupting major websites and government services. The incident, which Amazon attributes to a latent defect, has led to the global disabling of the faulty DNS automation and is estimated to have caused hundreds of billions of dollars in damage, prompting AWS to implement new safeguards to prevent future occurrences.
Amazon Web Services (AWS) experienced a significant, day-long outage in its US-EAST-1 region, commencing October 19, severely disrupting major websites and government services. The root cause was a race condition in DynamoDB's automated DNS management system, which created an empty DNS record due to a "latent defect" in its Enactor component. This critical fault prevented automated updates and led to widespread DNS failures. The initial DynamoDB failure cascaded, impacting core AWS services like EC2 instance launches and network configurations, subsequently affecting dependent services such as Lambda and Elastic Container Service (ECS). Recovery was complicated by the DropletWorkflow Manager (DWFM) entering "congestive collapse" and a massive backlog in Network Manager, prolonging the disruption. The incident's damage estimates are potentially "hundreds of billions of dollars," reflecting extensive business disruption. AWS has globally disabled the problematic DynamoDB DNS Planner and Enactor automation, committing to implementing new safeguards and reducing future recovery times. This event underscores the critical infrastructure risks associated with cloud dependency.
AI-powered research, real-time alerts, and portfolio analytics for institutional investors.
Request a DemoOverall Sentiment
extremely negative
Sentiment Score
-0.90
Ticker Sentiment
