Summary

What it is

A distributed storage system providing object, block, and file storage in a unified platform. S3 compatibility via its RADOS Gateway (RGW).

Where it fits

Ceph is the enterprise-grade, self-managed storage platform for organizations that need S3-compatible object storage alongside block and file access from a single infrastructure.

Misconceptions / Traps

Ceph is not just an object store — it is a unified storage platform. The S3 gateway is one component. Operational complexity is significantly higher than MinIO.
S3 API coverage in Ceph RGW is broad but not complete. Test specific API operations (multipart uploads, lifecycle policies) before production use.

Key Connections

implements S3 API — via RADOS Gateway
solves Vendor Lock-In — self-hosted deployment option
scoped_to S3, Object Storage — participates in the S3-compatible ecosystem

Definition

What it is

A distributed storage system providing object, block, and file storage in a single unified platform. Exposes S3 compatibility through its RADOS Gateway (RGW) component.

Why it exists

Infrastructure operators need a single storage platform that can serve multiple protocols. Ceph's S3 gateway allows existing S3 workloads to run against self-managed, software-defined storage.

Primary use cases

Unified on-premise storage, S3-compatible private cloud, research and academic data infrastructure.

Recent developments

Latest signals

Q1 2026 Newsletter — community substrate is being rebuilt deliberately. The Ceph Foundation is shifting from one global mega-event toward a network of regional Ceph Days — India drew 192 attendees, Raleigh 78, both larger than recent global gatherings. Ceph Tech Talks, the project's main on-ramp for new operators, has officially returned after a long gap. The project Slack moved to Pro tier — a small but telling signal that the Foundation is investing in collaboration infrastructure rather than living on free OSS goodwill. Documentation is the explicit Q1 priority: easier adoption for new users, easier scale-out for experienced operators.
Ceph Days Raleigh 2026 (March 25, 2026) — In-person practitioner conference covering Ceph operations, new feature surfaces across RADOS / RBD / CephFS / RGW, and migration patterns between Ceph versions and from competitor stacks. Treat this as the canonical 2026 surface for "what's actually being deployed in production" — talks consistently surface the day-to-day pain points that don't show up in release notes.
Rook + CSI is the Kubernetes story. Rook (the Kubernetes operator that deploys and manages Ceph as a CRD-backed storage layer) plus CSI (the standard volume-provisioning interface) is now the canonical recommended path for running Ceph on Kubernetes — both for object (RGW), block (RBD), and file (CephFS). Practitioner guides published in 2026 emphasize tracking release notes per Ceph component separately (RADOS / RBD / CephFS / RGW) rather than treating Ceph as one monolithic version, because behavior changes land on different cadences in each subsystem.
Operational signals from the field — what's biting users. Two recurring failure modes are showing up in 2026 community channels: (1) a 5-node Ceph 19.2.3 cluster freezing on node reentry under STP ring-topology peering storms (a Spanning Tree Protocol misconfiguration cascading into Ceph's monitor quorum, reported on the Proxmox forum) — points to fragility when Ceph's network topology assumes flat L2 but operators run STP on the underlay; and (2) CephFS outages following Debian Trixie upgrade or reboot cycles, where the metadata server fails to rejoin cleanly. Community runbooks now lean harder on total-power-loss recovery procedure — a sign that operators are hitting hard-failure scenarios more often than the "graceful failover" guarantees the docs imply. If you're running Ceph in production in 2026, those two issue classes are worth pre-rehearsing.