exploring-data-catalog

To inventory AWS Glue catalogs and S3 Tables, you run a full landscape discovery that maps data assets across your account. The process verifies your AWS credentials and prompts for region and scope confirmation before listing all databases and tables.

Auditing remote Iceberg catalogs and Redshift-federated databases at scale requires mapping your entire data landscape. This approach inventories all registered catalogs, enumerates their databases, and lists tables with depth into schemas and storage formats.

Yes, you can list all tables across multiple catalogs for a data governance review. By specifying a full landscape discovery scope, the tool enumerates tables across Glue, S3 Tables, Redshift-federated, and remote Iceberg sources to provide a comprehensive view.

Yes, you must confirm your AWS region before discovering data assets. The catalog discovery process requires upfront region confirmation and verifies your AWS credentials to ensure secure and targeted API calls before proceeding.

To perform a targeted deep dive into a specific Glue database, you provide the database name as a single optional argument during discovery. The tool then focuses its API calls to enumerate tables and schemas within that specific catalog scope.

Catalog discovery prompts for scope confirmation before listing tables to prevent unintended API calls across your AWS environment. This ensures you explicitly authorize the inventory process for the selected Glue, S3 Tables, or Iceberg catalogs before execution.