# Happy 20th Birthday, SQS! Two Decades of Quiet, Steady Evolution

Hey, it's Shiichan, listen to this! Today's news is about one of AWS's quiet workhorses turning 20 years old.

## What was announced?

The AWS Blog published a retrospective marking the 20th anniversary of Amazon Simple Queue Service (SQS). SQS launched on July 13, 2006, as one of AWS's very first services, alongside Amazon EC2 and Amazon S3.

The post touches on why SQS exists in the first place, distributed systems need a reliable way to pass messages between components without tight dependencies, and then walks through updates from the last five years (2021-2026) in particular.

## Why it matters

In a distributed system, if one service calls another directly, a slowdown on one side can drag the whole thing down. SQS solves that by putting a queue in between, decoupling components from each other. The fact that this idea has kept services running for 20 years straight says a lot about how universal that pattern still is.

## What changes

Even just in the past five years, SQS has kept evolving quietly but steadily. Here are the major milestones:

- Throughput: FIFO queue high-throughput mode scaled from 3,000 TPS in 2021 up to 70,000 TPS by November 2023
- Security: SSE-SQS (AWS-managed key encryption) arrived in November 2021, and encryption became the default for new queues in October 2022
- Access control: Tag-based ABAC (attribute-based access control) support landed in November 2022
- Protocol: A JSON protocol arrived in November 2023, cutting latency by up to 23% for 5 KB messages
- Large messages: The Extended Client Library for Python, supporting messages up to 2 GB, arrived in February 2024
- FIFO limits: The FIFO in-flight message limit expanded from 20,000 to 120,000 in November 2024
- Payload size: Maximum message payload grew from 256 KiB to 1 MiB in August 2025
- Integrations: EventBridge Pipes integration arrived in November 2023, letting you connect to other services with no custom code
- Multi-tenancy: Fair Queues arrived in July 2025 to address "noisy neighbor" problems where one user hogs a shared queue

## Dive Deep

The post notes that this evolution is now extending into AI workloads too, buffering requests to large language models and coordinating communication between autonomous AI agents. It's a nice full-circle moment: the same decoupled-messaging idea from 20 years ago is still doing real work in today's AI agent world.

## Wrap-up

- Amazon SQS turns 20, having launched on July 13, 2006
- FIFO queue throughput grew from 3,000 TPS to 70,000 TPS, and message payload limits from 256 KiB to 1 MiB
- Security and operations kept evolving too, with encryption (SSE-SQS, default encryption), ABAC, EventBridge Pipes integration, and Fair Queues
- More recently, SQS has started supporting AI workloads like buffering LLM requests and coordinating AI agents

There's something reassuring about seeing infrastructure this old keep evolving. Worth a read whether you're already using SQS or thinking about messaging for your AI agents.