Skip to Content

Supported connectors

Connect Amazon Athena

Connect Amazon Athena with an AWS access key.

Before you start

  • You are an Admin or a Developer, or your role has the datasource Connect permission.
  • You have an IAM user or role that can run Athena queries, read the Glue catalog and read the S3 results location.

Connect

  1. Go to Data Studio > Datasources and select Connect data source.

    Datasources page with the Connect data source button outlined
    Connect data source is at the top right of the Datasources page.
  2. Select Athena. You can type the name in Search connectors.

    Add datasource page with the Athena tile outlined
    The Athena tile on the Add datasource page.
  3. Fill in the form:

    FieldWhat to enter
    Datasource nameHow this datasource appears in lists and pickers, for example Production warehouse.
    S3 RegionThe region of the bucket Athena writes results to, for example us-east-1.
    S3 Access Key ID, S3 Secret Access KeyThe access key of the IAM user.
    DatabaseThe Athena database, for example iceberg_db.
    S3 Bucket NameThe bucket from the query result location, for example s3://your-bucket-name/path.
  4. Select Connect datasource.

Connect Athena form with the connect button outlined and the Setup guide on the right
Fill in the form, then select the button at the bottom. The Setup guide on the right lists the grants and where each value comes from.

Databrain checks the connection and reads your schema. You see Step 3 of 3 with Model your data. Next, create a datamart.

Give the IAM user access

The IAM user or role needs at least these actions:

athena:StartQueryExecution
glue:GetTables
s3:GetObject

Where to find the values

  • Region: S3 console > the results bucket > Properties.
  • Access key: IAM > your user > Security credentials > Create access key.
  • Database: the left panel of the Athena console.
  • Bucket: Athena console > Settings > Query result location.

If something goes wrong

If the check fails, the datasource stays on the form with Needs credentials. Fix the field the message names and select Connect datasource again.

  • The database did not answer in time. A firewall blocks Databrain. Allow the outbound IP on the database port.
  • The database rejected these credentials. Check the username and password, and that the user can sign in from a remote host.
  • The credentials worked, but the user cannot read the catalogue. Run the grants above.

On this page