Lack of portable S3 Tables alternatives for multi-cloud
π§ workproduct problemSingle report βββββ
A developer reports that AWS S3 Tables is locked to the AWS ecosystem, forcing teams running self-hosted or multi-cloud infrastructure to choose between high-overhead metadata management or overly complex storage solutions like Ceph to achieve similar Iceberg-based functionality.
What people do today
- Using regular S3 with separate catalogs like Hive or Glue
- Deploying Apache Ozone or Ceph with Iceberg
- Manual metadata management
π§ Fix this
Ideas a builder, maker or community group could start on:
- Develop an open-source, vendor-neutral storage layer that implements native Iceberg table support for any S3-compatible object store.
- Create a lightweight, containerized metadata catalog service designed specifically for small teams to manage Iceberg tables without heavy infrastructure.
- Build a migration tool that automates the translation of AWS S3 Tables metadata into a portable, open-standard format for cross-cloud compatibility.
Real voices
βthe native S3 Tables implementation is locked inside AWS. For those of us running self-hosted or multi-cloud, what are the current options?β
Related problems
π§ workproduct13 reports
Indeed job feed ignores user preferences
π§ workproduct10 reportsInability to filter AI-generated content on LinkedIn
π§ workproduct8 reportsLinkedIn login verification loop
FixHumanityDaily
The most important new problems, and ideas to fix them, in your inbox.
Placeholder: no data is collected yet.