AWS Glue
AWS Glue Data Catalog can act as the catalog for Iceberg tables stored in AWS.
Connect Glue to Altertable when Glue is the source of truth for table metadata and Altertable should query those Iceberg tables alongside other lakehouse data.
Prerequisites
Prepare the AWS account ID, region, and IAM role ARN. The role must allow reading Glue catalog metadata and the underlying Iceberg objects. Configure its trust relationship for the principal that will assume it; obtain the required trust details for your Altertable environment before saving the connection.
A read-only policy must cover:
glue:GetDatabase,glue:GetDatabases,glue:GetTable, andglue:GetTableson the catalog, intended databases, and tables.s3:ListBucketon the data bucket, scoped to the relevant prefixes.s3:GetObjecton those prefixes, including Iceberg metadata, manifests, and data files.kms:Decrypton the key when those objects use customer-managed KMS encryption.
If AWS Lake Formation governs the tables, configure its permissions as well as IAM. Use the AWS Glue IAM guide to scope the role and its trust policy.
Connect AWS Glue
- Create or choose an IAM role with the Glue and storage permissions required for the tables Altertable should query.
- Open Catalogs in the Altertable app.
- Click New catalog.
- Select AWS Glue.
- Enter the AWS account ID, region, and role ARN.
- Save the catalog, then query the Glue-backed tables with SQL.
Scope the IAM role to the catalogs, databases, tables, and storage locations Altertable needs. If table data is encrypted with AWS KMS, include the required decrypt permissions.
Verify the connection
Open the saved catalog and check that the intended database and tables appear. In SQL Explorer, replace the example names and read a known table:
SELECT * FROM my_catalog.my_database.my_table LIMIT 10;
Compare a known record with its source and inspect the returned column types. Metadata discovery alone does not verify S3 access.
Troubleshooting
- Role cannot be assumed: check the role ARN and trust policy for the configured environment.
- Database or table is missing: check the region, Glue IAM resources, and Lake Formation grants.
- Tables appear but data cannot be read: check S3 prefixes, object permissions, and KMS decrypt access.
- Schema changed upstream: inspect the source table metadata and recheck the catalog before changing queries.