Getting started with Apache Iceberg write support in Amazon Redshift – Part 2

Redshift's native Iceberg write support eliminates a critical friction point I've seen repeatedly: teams building lakehouse architectures were forced to choose between analytical simplicity and data mutation capabilities. Now you can perform row-level updates and deletes directly in Redshift without staging data or managing separate operational databases. This matters because it collapses your data movement patterns. Instead of streaming changes into a separate OLTP system, then batch-syncing back to your lake, you operate against a single source of truth. The architectural win is cleaner lineage and fewer failure points, but the operational win is what actually gets my attention—fewer jobs to orchestrate, simpler monitoring, reduced storage sprawl from managing multiple datasets. For teams already invested in S3 and Redshift, this is a force multiplier. The broader signal: cloud platforms are converging on open table formats specifically because proprietary lock-in became a liability. If you're still debating Iceberg versus Delta versus proprietary formats, Redshift's expansion confirms the industry consensus. Start prototyping your mutation patterns now, especially for slowly-changing dimensions and correction workflows.