S3 Tables Add Full Apache Iceberg V3 Support

S3 Tables now support the full Apache Iceberg V3 specification. This is not a minor spec bump; it's a significant alignment for data lake tooling.

What changed

• Amazon S3 Tables now support all data types defined in the Apache Iceberg V3 specification.
• Support includes column default values, deletion vectors, and row lineage.
• Existing Iceberg V2 tables can be upgraded to V3.

Why it matters

This announcement closes a significant gap for organizations using S3 Tables as their data lake foundation. Previously, limited Iceberg spec support meant users had to work around missing data types, default values, or advanced features like deletion vectors. The honest version: This makes S3 Tables a more viable, out-of-the-box option for workloads that rely heavily on the full Iceberg specification, particularly those migrating from or interoperating with other data lake platforms. It reduces the engineering effort required to maintain feature parity.

The catch

The catch: While S3 Tables now support V3, the announcement does not specify the performance implications of these new features, particularly for row lineage or deletion vectors. Furthermore, the upgrade path from V2 to V3 is not detailed, nor are potential costs associated with the underlying S3 operations that these features might trigger. Pairs with: AWS Glue Data Catalog will be critical for managing these enhanced tables.

Ship it

For teams currently using S3 Tables with Iceberg V2, evaluate upgrading to V3 if your workloads require the newly supported data types or features like deletion vectors. For new data lake initiatives, consider S3 Tables with V3 as a primary option, especially if you are already invested in the AWS ecosystem and require robust Iceberg compatibility without managing separate metastore infrastructure. This is especially relevant for workloads in us-east-1.

Bottom line: S3 Tables now fully support Apache Iceberg V3, simplifying data lake integrations but requiring validation of performance and upgrade paths.

— Filed to /blog