Amazon Athena

Supported Data warehouses & lakehouses

Catalog AWS Glue Data Catalog databases, tables, views and columns queried through Amazon Athena.

Capabilities

CapabilitySupportNotes
Tables, views & columns Supported
Keys, constraints & indexes Not available
Procedures & functions Not available
Data lineage Partial
Lineage from query history Not available
Business glossary links Supported
Data quality probes Supported
Data profiling Supported
Data classification Supported
Chat with your data Supported

Connection settings

Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing Amazon Athena in the technology step.

Driver classcom.simba.athena.jdbc.Driver
JDBC URLjdbc:athena://athena.us-east-1.amazonaws.com:443
Authentication
Service principal (shared technical user)
User principal (personal credentials, BYOC)
Ephemeral credentials (asked at each run)
Crawling strategyJDBC or SQL

Connection properties

PropertyDescription
S3OutputLocationS3 location where Athena writes query results.
AwsRegionAWS region of the Athena workgroup.

The Blindata Agent does not include this driver: download the vendor JDBC driver and copy the .jar into the agent drivers folder, as described in Add JDBC drivers. Driver properties can be added under Advanced settings in the connection wizard.

Prerequisites & permissions

  • A Blindata Agent installed with network access to Amazon Athena.
  • The vendor JDBC driver installed on the agent (see Add JDBC drivers).
  • An IAM principal with athena:StartQueryExecution, athena:GetQueryResults and glue:Get* on the catalog.
  • Write access to the S3 output location; read access to the S3 data for data quality and profiling.

Set up metadata crawling

  1. Create the connection to Amazon Athena on the agent (see Connection settings) and use Test to verify it.
  2. Create or open the system that represents Amazon Athena in the catalog and link it to the connection.
  3. In the CRAWLING tab add a crawling job with strategy JDBC or SQL.
  4. Run a TEST to check the number of extracted objects, then RUN or schedule the job.

The job options and the column aliases of every extraction query are described in the Generic JDBC reference.