AWS adds a managed route from Hive tables to Iceberg
AWS has announced a migration feature for S3 Tables that moves eligible Hive tables into Iceberg. The company says it handles the conversion workflow, with a short interruption still required for the final switch.
Published
What AWS is changing
AWS announced a managed conversion feature for its S3 Tables service. It takes existing Hive tables registered through Glue and builds an Iceberg destination. The company describes this as an alternative to assembling a migration system yourself.
How the switch works
According to AWS, the process first checks the source and produces a compatibility report. It then copies the data. Customers can run further synchronisations to bring the destination up to date while writes continue at the source. AWS still specifies a few minutes without writes at cutover; the feature does not promise a completely interruption-free move.
Limits worth checking
At launch, AWS says the feature covers Parquet data held in S3, with the source and destination restricted to the same account and region. AWS lists availability in selected regions in the US, Asia Pacific and Europe. The destination starts read-only during migration and becomes writable after completion.
Where this comes from
This report is based on the reporting and source material below. Announcements and company claims are attributed, rather than treated as independent tests.
- AWS News — Amazon S3 Tables now offer managed migration of Apache Hive tables to Apache Iceberg ↗Published 4 十一月 2026
Something needs correcting? Report a correction.
