AWS Outage Explained Simply — What Happened and Which Services Were Impacted

🪩 Introduction

If you've noticed your favorite apps slowing down or not loading recently, you're not alone. And even if you didn't notice, I'm sure you've read or heard about it somewhere...
On 20th October 2025, Amazon Web Services (AWS) — the backbone of much of the internet — faced a major outage centered in its US-East-1 (Northern Virginia) region.

The issue started with a DNS failure that disrupted Amazon DynamoDB, one of AWS’s most critical databases.
Since so many other AWS services depend on DynamoDB for user sessions, configuration data, or authentication, the impact spread rapidly across the cloud ecosystem.

Interestingly, AWS engineers later found that the disruption was amplified by one of their own internal monitoring tools. The tool, designed to detect and report abnormal activity, began triggering false alerts due to a configuration issue. These alerts cascaded through internal systems, forcing automated recovery protocols to activate unnecessarily — which further strained service capacity and extended the outage duration.

Now, you might be wondering why a database going down affected so many users and other services or companies that didn't use it directly. It caused a "Domino Effect"!

Let's explore which services were impacted and how they are interconnected within AWS.

⚙️ Key AWS Services Impacted

Let’s look at the key services affected — and how the DynamoDB + DNS issue caused a chain reaction across them.

1. Amazon DynamoDB

• What it is: A fully managed NoSQL database used by millions of apps for fast data access.

• What happened: The DNS issue stopped DynamoDB endpoints from being reachable in US-East-1.

• Impact: Apps couldn’t read or write data — user sessions, product data, or app states failed to load.

2. AWS Identity and Access Management (IAM)

• What it is: Controls who can access which AWS resources.

• How it was impacted: IAM stores and validates temporary credentials using DynamoDB tables.

• Effect: Authentication and authorization calls began failing — stopping services like Lambda, S3, and EC2 from verifying access tokens.

3. AWS Lambda

• What it is: Runs your code without servers.

• How it was impacted: Many Lambda functions interact with DynamoDB. With DNS resolution failing, function invocations started timing out.

• Effect: Event-driven systems (like API calls or SQS triggers) broke mid-execution.

4. Amazon Simple Queue Service (SQS)

• What it is: Passes messages between different parts of an app.

• How it was impacted: SQS often triggers Lambda functions or stores metadata in DynamoDB.

• Effect: Queued messages piled up without being processed.

5. Amazon Elastic Compute Cloud (EC2)

• What it is: Provides cloud servers.

• How it was impacted: Existing EC2 instances ran fine, but the control plane (which handles scaling or launching new ones) depends on IAM and DynamoDB.

• Effect: Auto-scaling, instance launches, and terminations failed temporarily.

6. Elastic Load Balancing (ALB/NLB)

• What it is: Distributes web traffic across multiple servers.

• How it was impacted: Load balancers rely on DNS and health checks.

• Effect: Some targets were falsely marked unhealthy or unreachable, causing traffic drops.

7. DynamoDB Global Tables

• What it is: Keeps DynamoDB data synced across regions.

• How it was impacted: Since US-East-1 was unreachable, replication stalled.

• Effect: Apps in other regions saw outdated or incomplete data.

8. Amazon Cognito

• What it is: Manages user logins and sessions for apps.

• How it was impacted: Cognito stores session and user data in DynamoDB.

• Effect: Login and token refresh operations failed, locking users out of many apps.

9. AWS Control Plane Services

• What it is: The “management layer” that powers the AWS Console and APIs.

• How it was impacted: These services use DynamoDB to track resource states.

• Effect: Developers couldn’t create, modify, or delete AWS resources from the console or CLI for several hours.

10. Amazon S3

• What it is: AWS’s object storage service for files, images, and backups.

• How it was impacted: S3 itself ran mostly fine, but access policies and authentication (via IAM and Cognito) failed intermittently.

• Effect: Some users experienced failed uploads or downloads in US-East-1.

Besides this, many other services like CloudWatch, Step Functions, and API Gateway were not directly dependent on DynamoDB but were affected due to AWS's internal connections.

📉 The Overall Impact (In Simple Terms)

• Apps that relied on logins, data access, or background jobs failed temporarily.

• Large-scale apps and websites like e-commerce, streaming, and dashboards faced major slowdowns.

• US-East-1 being the primary hub meant even apps hosted in other regions felt the heat due to dependency routing.

🧠 Key Takeaway

This outage was a strong reminder that AWS services are deeply interconnected.
A single component — in this case, DNS + DynamoDB — can cascade into multiple dependent systems, even across regions.

It showed that in cloud computing, resilience isn’t just about redundancy — it’s about understanding how your architecture depends on shared services.

Follow me :

X (formerly twitter) : Ruchir Dixit

LinkedIn : Ruchir Dixit