AWS announced S3 Tables earlier this year, and the integration with Iceberg is clearly the direction for AI/analytics data stacks. But the native S3 Tables implementation is locked inside AWS.
For those of us running self-hosted or multi-cloud, what are the current options?
Using regular S3 + separate catalog (Hive/Glue/Polaris) – metadata overhead and extra ops
Apache Ozone / Ceph + Iceberg – seems heavy for smaller teams
Something else I'm missing?
I've seen rumors about open-source projects adding native Iceberg table support directly in the storage layer (basically S3 Tables but portable). Would that actually help? What's the #1 pain point you'd want solved?
Curious to hear from people who tried to run Iceberg workloads outside AWS.
0 comments
—
Ask HN: Are we going to see a portable S3 Tables alternative outside AWS? · HackerTrans
For those of us running self-hosted or multi-cloud, what are the current options?
Using regular S3 + separate catalog (Hive/Glue/Polaris) – metadata overhead and extra ops
Apache Ozone / Ceph + Iceberg – seems heavy for smaller teams
Something else I'm missing?
I've seen rumors about open-source projects adding native Iceberg table support directly in the storage layer (basically S3 Tables but portable). Would that actually help? What's the #1 pain point you'd want solved?
Curious to hear from people who tried to run Iceberg workloads outside AWS.