Amazon Athena
Connect Amazon Athena to Lakehousecat using AWS credentials. Athena does not use a traditional connection URI — authentication is handled via IAM access keys.
Connection Fields
| Field | Required | Default | Description |
|---|---|---|---|
| S3 Staging Dir | Yes | — | S3 output location for query results. Example: s3://my-bucket/athena-results/ |
| AWS Region | Yes | — | AWS region where Athena is running. Example: eu-central-1 |
| AWS Access Key ID | Yes | — | IAM access key ID |
| AWS Secret Access Key | Yes | — | IAM secret access key |
| Database / Schema | No | default | Athena database name in the AWS Glue Data Catalog |
| Workgroup | No | primary | Athena workgroup to use for query execution |
AWS IAM Requirements
The IAM user or role must have the following minimum permissions:
athena:StartQueryExecutionathena:GetQueryExecutionathena:GetQueryResultss3:GetBucketLocationon the staging buckets3:PutObject,s3:GetObject,s3:ListBucketon the staging bucketglue:GetDatabases,glue:GetTables,glue:GetTablefor schema discovery
Workgroup Configuration
The selected workgroup must either have a default output location configured in its settings, or the S3 Staging Dir field must be filled in when creating the datasource. If neither is set, queries will fail.
Recommendation: create a dedicated workgroup with an output location pre-configured in the AWS Console under Athena → Workgroups.
Notes
- SSH Tunnel: not supported
- Athena uses the AWS Glue Data Catalog as its metadata store
- All data resides in S3 — Athena has no dedicated storage layer
- Costs are based on the amount of data scanned per query
Next Steps
After creating the datasource, go to the Operations tab to trigger semantic extraction.