Topic

Directory Buckets / Hot Object Storage

A purpose-built storage tier designed for single-digit millisecond latency, using a directory-based namespace within a single Availability Zone. Trades multi-AZ durability for consistently low access times.

4 connections 3 resources

Summary

What it is

A purpose-built storage tier designed for single-digit millisecond latency, using a directory-based namespace within a single Availability Zone. Trades multi-AZ durability for consistently low access times.

Where it fits

Directory Buckets represent the high-performance end of S3 storage. They fill the gap between standard S3 (high durability, variable latency) and local disk (low latency, no durability), enabling latency-sensitive workloads like ML training and real-time analytics to use object storage.

Misconceptions / Traps
  • Directory Buckets are single-AZ only. Data is not replicated across AZs, so they are not suitable as a sole durable store for critical data.
  • The directory-based namespace is not the same as a filesystem. It enables faster listing within directory structures but does not provide POSIX semantics.
Key Connections
  • scoped_to S3, Object Storage — a specialized storage tier within the S3 ecosystem
  • S3 Express One Zone implements Directory Buckets / Hot Object Storage — the AWS implementation
  • solves Cold Scan Latency — single-digit ms access eliminates cold-start overhead
  • constrained_by Vendor Lock-In — currently an AWS-specific feature

Definition

What it is

Purpose-built storage tier for single-digit millisecond latency, using directory-based namespace within a single Availability Zone. Trades multi-AZ durability for dramatically reduced latency.

Why it exists

Standard S3 has ~50-100ms per-request latency. AI/ML inference, real-time analytics, and interactive workloads need lower latency. Directory buckets co-locate data with compute for speed.

Connections 4

Outbound 2
Inbound 2

Resources 3