AWS Snowflake Lakehouse: 2 Practical Apache Iceberg Integration Patterns

Original Japanese article: AWSのレイクハウス（Apache Iceberg）をSnowflakeと連携する2つのパターンを整理する Introduction I'm Aki, an AWS Community Builder (@jitepengin). In recent years, it has become increasingly common to build lakehouse architectures centered around Apache Iceberg. Before the rise of lakehouse architecture, it was common to design systems where data was consolidated into a specific platform, such as: an architecture centered around Amazon Redshift on AWS an architecture centered around internal tables in Snowflake However, with the advent of Apache Iceberg, this assumption is rapidly changing. Now that data on Amazon S3 can be directly accessed from multiple engines, what matters is no longer simply product selection. Instead, the architecture design itself has become the central focus: where the data resides, who owns the write responsibility, and who holds governance authority. In this article, focusing on the coexistence of AWS and Snowflake, I will organize the following: two patterns bas