Closing the Resilience Gap in Your AWS Data Lakehouse

Most enterprises running AI and analytics on AWS have Apache Iceberg sitting at the center of their data lakehouse. It's the layer that makes everything queryable, but it's also the layer almost nobody has a real recovery plan for.

That used to be an acceptable gap. It isn't anymore. The data sitting in those tables now feeds ML models, real-time decisioning, and financial reporting. When it goes down, your whole business goes with it.

In this fireside chat, Rubrik and AWS get into what it actually takes to protect a production data lakehouse and what real recovery looks like when something goes wrong.

What we'll cover:

• Why the lakehouse has quietly become the most business-critical layer in the modern data stack, and what that means for how you think about resilience
• What catalog-aware recovery is, why it matters, and why it's the step most incident response plans don't account for
• How Rubrik and AWS protect the full lakehouse stack with independent backup stored outside your account and automatic catalog recovery on restore