LakeBase

LakeBase Clusters expose a PostgreSQL JDBC endpoint that you can connect to from any PostgreSQL-compatible client. Queries run on Spark under the hood — see Spark SQL syntax for the query dialect.

Catalog and Access Control Modes

A LakeBase Cluster runs in one of three modes. The mode determines how you authenticate and which driver you need.

Mode	Authentication	Authorization	Driver
Onehouse Catalog	Username/password from the cluster connection details page	Onehouse EKS node role	Standard PostgreSQL JDBC driver
Glue Catalog	Username/password from the cluster connection details page	Onehouse EKS node role	Standard PostgreSQL JDBC driver
Glue Catalog with Lake Formation	Corporate identity provider (IdP) via browser OAuth	Lake Formation	Onehouse LakeBase JDBC driver

See Get Connection Details for where to find the endpoint and credentials, and LakeBase JDBC Driver: Identity Provider Integration for the full list of supported IdPs and their driver properties.

Connecting with Lake Formation

When using Lake Formation for access control, you can optionally specify an IAM role to assume for querying. If you don't specify a role, the first IAM role from your authentication token is used by default.

To specify a different IAM role, add it to the connection using the options parameter:

jdbc:postgresql://host:5432/postgres?options=-c onehouse.lakebase_iam_role=arn:aws:iam::account:role/role-name

Client Integrations

• Connect with DBeaver
• Connect from a Java client
• Connect from a Python client
• Connect from psql

warning

If you are using a tool not listed here, please contact Onehouse support for assistance.

Network Access

By default, LakeBase Clusters only accept traffic from within your VPC. To connect from outside the VPC (e.g., your laptop), follow Connect to your VPC to set up a VPN or bastion host.