TechnologyNov 18, 20263 min read

Protecting Apache Iceberg Lakehouses at Scale with Rubrik on AWS


Many organizations running production analytics and artificial intelligence (AI) on Amazon Web Services (AWS) have standardized on Apache Iceberg as their open table format. AWS-native services like AWS Glue, Amazon Simple Storage Service (Amazon S3), and Amazon S3 Tables have simplified managing Iceberg tables at scale. As these tables have become more central to the business, a gap has become apparent. 

Recovering an Iceberg table after a data loss event is more involved than recovering the files it is made of. Copying the underlying files back is comparatively straightforward. Restoring a table that is in fact queryable, with its metadata, manifests, and catalog all consistent, is not. This matters more than it used to, because the data behind these tables now serves as the input layer for machine learning (ML) model training, real-time decisioning, and financial reporting. When that data becomes unavailable, the impact extends well beyond storage.

In this post (originally published on AWS Blogs), we discuss why the data lakehouse has become a protection surface in its own right, why Apache Iceberg’s built-in tools were not designed to serve as an independent recovery layer, and how Rubrik, an AWS Partner, addresses this with Apache Iceberg Data Protection built natively on AWS.

Continue reading…

 

Related Articles