> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Metabase

> Connect Metabase to the e6data query engine using the e6data driver.

Metabase is an open-source business intelligence tool for exploring and visualizing data. This guide connects Metabase to the e6data query engine.

## Requirements

* A running instance of Metabase (see the [Metabase docs](https://www.metabase.com/docs/latest) for installation).
* The latest [e6data JDBC driver](/query/connect/jdbc).
* A Direct or TLS connection on your cluster.
* The connection details from the cluster's **Connection Information** tab - host, port, catalog, database, username, and password (a [personal access token](/platform/tokens/pat-and-service-account-keys)).

## Connect

1. **Deploy the e6data driver.** Download the latest e6data Metabase driver JAR, copy it into the Metabase `/plugins/` directory, and restart Metabase to load it.
2. Open the Metabase web interface and go to the gear icon → **Admin settings → Databases → Add a database**.
3. Enter the connection parameters:
   * **Database Type**: `e6data`
   * **Display Name**: a name for the database in Metabase
   * **Host**: the cluster's IP address or domain name
   * **Port**: the cluster port (for example, `80`)
   * **Catalog**: the catalog attached to the cluster
   * **Database**: the database within that catalog
   * **Username**: your e6data login
   * **Password**: a personal access token
4. Add JDBC string parameters as needed:
   * **Direct connectivity**: `AUTO_RESUME=true` (optional) to enable cluster auto-resume.
   * **TLS connectivity**: `secure=true` (required), `cluster-uuid=<uuid>` (required), and optionally `AUTO_RESUME=true`.

<Info>
  Following the steps in this order results in a successful connection to e6data through Metabase.
</Info>

## TLS/HTTPS

e6data uses globally trusted certificates, so the host and port from the connection dialog are sufficient. Any cluster requiring authentication also requires TLS/HTTPS - use the cluster's HTTPS URL in the connection string.

## See also

* [JDBC](/query/connect/jdbc)
* [Endpoints and cluster ingress](/query/clusters/ingress)
* [Access tokens](/platform/tokens/pat-and-service-account-keys)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.