Connector
Amazon Athena
Query data in S3 with Amazon Athena: the tables your data catalog already tracks, with no cluster to run.
Settings
What the connection form asks for. Every connection has a Staging side, which it needs, and an optional Production side with values of its own; both ask for the same settings.
| Region | |
| Default database | Used when a node names a table without qualifying it (e.g. orders rather than sales.orders). |
| Data catalog | Blank uses AwsDataCatalog, the standard Glue catalog. Set it only for a federated or external catalog. |
| Workgroup | Blank uses the account's primary workgroup. |
| Output Location (S3) | S3 URI where Athena writes query results, e.g. s3://my-bucket/athena/. Required unless the workgroup enforces its own. |
| Endpoint (optional) | Set only for a PrivateLink/VPC endpoint, a FIPS endpoint, or GovCloud. Blank uses the standard regional endpoint. |
| Access Key ID | Leave blank to use the server's IAM role / instance profile. |
| Secret Access Key | Leave blank to use the server's IAM role / instance profile. Stored encrypted, and never shown again after you save it. |
Testing the connection
Test lists the data catalog's databases. That costs nothing and needs no query output location, and it still proves the region, the credentials and the catalog access.
Good to know
- A wrong or expired key fails Test. A real key that is not allowed to do what Test asks still passes, because AWS checks the signature before the permissions.
- Leaving the keys blank uses the server's own IAM role, and only on a shared connection an administrator manages; a personal connection must carry its own keys.