How-to guideApplies to: Unified engine deployments
Register AWS Glue Iceberg REST and read a table with the selected AWS identity.
Before you start
Use an existing catalog with at least one readable Iceberg table. The engine and
workers must reach the catalog and its table storage. Have the remote identity
and permissions ready before creating the Unified registration. Replace the
namespace and table with one you know has data.
The identity comes from the engine runtime, not your browser or laptop. Grant
catalog metadata access and access to the actual table-file prefixes, including
any required KMS keys. Use the Glue Iceberg REST API URI supplied for the
region, with its account/warehouse value. Its signing service is glue. The
service must return usable temporary storage credentials, or the table location
must already have configured storage access in Unified. Requesting delegation
alone does not grant access.
Values to collect
- AWS region, namespace, table, and service-specific catalog identifiers.
- Runtime identity with access to the catalog and data.
Run the SQL
Replace every <placeholder> before running. Use unused names for the resources
below. Run the statements in order in Workbench.
Check the result
The SELECT should return up to five rows from the chosen table. Use a nonempty
table for this check. This verifies both metadata and table-file access;
creating the registration alone does not verify either.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
Last modified on November 4, 2026
