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

# Trino

> Connect a Trino coordinator to Genloop with host, catalog, and read-only credentials over HTTP or HTTPS, optionally through an SSH tunnel.

Genloop connects to a Trino coordinator over HTTP or HTTPS and queries a single catalog. Trino federates queries across the data sources its catalogs expose.

## Before you connect

* A Trino user with read access to the catalog you want to query.
* The **catalog** name Genloop should read, for example `hive` or `iceberg`.
* Network access from Genloop. If the coordinator is behind a firewall, allow Genloop's regional IP address. See [Before you begin](/using-genloop/connections/connect-a-database#before-you-begin).

## Connection fields

| Field               | Description                                                                              |
| ------------------- | ---------------------------------------------------------------------------------------- |
| **Connection name** | A name to identify this connection in Genloop                                            |
| **Host**            | Hostname or IP address of your Trino coordinator                                         |
| **Port**            | The port your Trino coordinator listens on. Defaults to `8443`                           |
| **Catalog**         | The catalog Genloop queries, for example `hive`                                          |
| **Username**        | Trino user Genloop connects as                                                           |
| **Password**        | Password for that user. Leave blank if your cluster does not use password authentication |
| **HTTP scheme**     | `https` by default. Set to `http` for a non-secure coordinator                           |

## Encryption (TLS)

Leave **HTTP scheme** set to `https` to connect securely. This is the recommended setting. Use `http` only for a coordinator that runs without TLS, for example inside a private network.

## Connect through an SSH tunnel

If the coordinator is not reachable directly, reach it through a bastion or jump host. Turn on **Connect via SSH tunnel** in the connection form and complete these fields.

| Field                   | Description                                                                                       |
| ----------------------- | ------------------------------------------------------------------------------------------------- |
| **SSH host**            | Public IP or DNS of the bastion. Cannot be `localhost`                                            |
| **SSH port**            | SSH port on the bastion. Default is `22`                                                          |
| **SSH username**        | User Genloop signs in to the bastion as                                                           |
| **PEM key**             | Your private key file. Sent encrypted with the rest of the credentials                            |
| **Remote bind address** | Coordinator host as seen from the bastion. Use `127.0.0.1` if the coordinator runs on the bastion |
| **Remote bind port**    | Coordinator port as reached from the bastion                                                      |

## Permissions

Genloop only reads your data. You can connect with any user that already has read access to the catalog you connect.

Access in Trino is managed through your access-control configuration rather than SQL grants. If you want a dedicated read-only user for Genloop, ask your Trino administrator to set one up.

## Next steps

<CardGroup cols={2}>
  <Card title="Connect a database" icon="database" href="/using-genloop/connections/connect-a-database">
    Back to the full connection flow.
  </Card>

  <Card title="Context Hub" icon="brain" href="/using-genloop/context-hub">
    View and edit the memory built from your connection.
  </Card>
</CardGroup>