Iceberg Catalog Interface

Run Apache Iceberg without external catalog infrastructure. AIStor embeds the Iceberg REST Catalog API directly into object storage, giving query engines a single endpoint for both metadata and data access.
close icon
Diagram showing Spark, Trino, and Flink connecting via REST API to AI STOR with a note below stating External Catalog Not Required.

Native Iceberg REST Catalog

Full Apache Iceberg REST API support built directly into AIStor—no external catalog services required.

Why AIStor is Different

Traditional Iceberg deployments require separate catalog infrastructure—Hive Metastore with its database dependencies or Nessie with additional service clusters. Each adds operational complexity, latency, and failure points between your query engines and your data. AIStor eliminates the catalog layer entirely.
Zero External Catalogs
No Hive Metastore, Nessie, or separate catalog infrastructure to manage
One Unified Endpoint
Single connection for both catalog operations and S3 data access
Native S3 Credentials
Query engines authenticate with existing S3 credentials—no Kerberos or custom auth
Atomic Multi-Table Commits
Transaction API ensures all table changes succeed together or roll back

Business Impact

Get the Technical Details

Iceberg REST Catalog support in AIStor is currently in technical preview.

Contact MinIO for early access to tech preview documentation, API specifications, query engine configuration examples, and guidance on evaluation environments for testing Iceberg catalog integration before general availability.
Smiling woman wearing glasses and a smartwatch looking at a silver laptop on a wooden table at home.

Ready to See It in Action?

Get AIStor running in your environment in minutes.

Additional Resources