Amazon S3 Tables adds managed migration of Apache Hive tables to Apache Iceberg
AWS says Amazon S3 Tables can now migrate Apache Hive datasets held in S3 into fully managed Apache Iceberg tables, with no pipelines to build and no compute to provision. The change matters to teams running Hive-based data lakes on Amazon S3.
What to do now
On 4 November 2026, AWS announced a new capability in Amazon S3 Tables: managed migration of existing Apache Hive tables to the Apache Iceberg format. Hive data already sitting in Amazon S3 can be moved into Iceberg tables managed by the S3 Tables service.
According to AWS, customers do not need to build transformation pipelines or provision compute capacity to carry out the migration. The company also says production workloads can keep running while the move takes place, which should remove the need for a dedicated downtime window.
For teams maintaining an older Hive-based data lake, this lowers the effort of moving to Iceberg, an open table format that has gained wide adoption. Until now such a switch generally relied on in-house scripts or rewrite jobs.
The source, a short summary on the AWS blog, does not state the pricing of the migration, the regions where it is available, or any limits on table size or layout. It also does not explain how existing query engines and tools need to be pointed at the new tables afterwards. Administrators should check the official documentation on these points before planning a migration.
What to do now
- Inventory the Apache Hive tables stored in Amazon S3 that are candidates for migration to S3 Tables.
- Check the AWS documentation for pricing, regional availability and limits of the managed migration, which the announcement does not detail.
- Trial the migration on a non-critical table and confirm that the applications and query engines reading it still work.
- As general good practice, review the access permissions applied to the new Iceberg tables once migrated.