Amazon Explains the Cause Behind Tuesday’s Massive AWS Outage

Amazon has published a post-event summary to shed some light on the root cause behind this week’s massive AWS outage that took down a long list of high-profile sites and online services, including Ring, Netflix, Amazon Prime Video, and Roku.

The outage started at roughly 10:30 AM EST on Tuesday. It affected the US-EAST-1 AWS region, which ensures connectivity for people and companies in the northeastern part of the United States.

As a result, streaming through Netflix, Amazon Prime, and Roku was immediately impacted together with Ring devices, brought down and unreachable, according to users reporting that they couldn’t connect to their cameras.

Also Read: 6 Simple Tips on Cyber Safety at Home

Around the same time, Amazon delivery employees began sharing on Reddit that they could no longer access internal apps required to scan packages, access delivery routes, or see upcoming schedules.

“At 7:30 AM PST, an automated activity to scale capacity of one of the AWS services hosted in the main AWS network triggered an unexpected behavior from a large number of clients inside the internal network,” Amazon explained in a summary of this incident.

“This resulted in a large surge of connection activity that overwhelmed the networking devices between the internal network and the main AWS network, resulting in delays for communication between these networks.

“These delays increased latency and errors for services communicating between these networks, resulting in even more connection attempts and retries. This led to persistent congestion and performance issues on the devices connecting the two networks.”

Our Support Contact Center also relies on the internal AWS network, so the ability to create support cases was impacted from 7:33 AM until 2:25 PM PST. We expect to release a new version of our Service Health Dashboard early next year that will make it easier to understand service impact and a new support system architecture that actively runs across multiple AWS regions to ensure we do not have delays in communicating with customers. – Amazon

The Tuesday AWS outage is definitely not unique as it follows multiple other similar events since 2011, including a large-scale incident that affected the same region in November 2020.

Also Read: 7 Key Principles of Privacy by Design that Businesses should adopt

When it happened, it also brought down a large number of sites and online platforms after Amazon’s Kinesis service for real-time processing of streaming data began experiencing issues.

One year prior, during September 2019, a power outage that hit the AWS US-EAST-1 data center in North Virginia caused data loss for all Amazon customers lacking working backups to restore their files.

In February 2017, an Amazon’s S3 (Simple Storage Service) outage took down millions of small and high-profile sites and online platforms, including Adobe’s apps and services, Docker, Mailchimp, Medium, Signal, Slack, Trello, Twilio, IFTTT, and Twitch.