Athena Overview and Discovery
Dynomate discovers Athena metadata with an AWS profile. It stores the discovery result locally so you can open a table and prepare a query.
What Dynomate discovers
Dynomate loads this hierarchy for each selected Region:
profile → Region → catalog → database → table
It also loads Athena workgroups and their query-result settings. Dynomate records the profile, AWS account, and Region with each result.
Discover Athena resources
- Open Table Discovery.
- Select an AWS profile.
- Complete SSO or MFA authentication when required.
- Select one or more Regions.
- Select Load Tables.
Discovery runs for the selected Regions. Dynomate limits concurrent metadata requests. A failure in one Athena branch does not remove successful results from other catalogs, databases, or Regions.
Review discovery results
- Expand the Athena result for a Region.
- Review any branch errors.
- Select Open for a table.
Dynomate stores successful metadata immediately. Run discovery again after you add, remove, or rename an Athena resource.
Required permissions
Dynomate calls these AWS actions during Athena discovery:
sts:GetCallerIdentityathena:ListDataCatalogsathena:ListDatabasesathena:ListTableMetadataathena:ListWorkGroupsathena:GetWorkGroup
Query execution needs additional Athena actions. The data source and result location can also require AWS Glue, Lake Formation, S3, and KMS access. Dynomate does not preflight those service policies. See Query Athena permissions.