Docs / Get warehouse credentials

Get warehouse credentials

Step-by-step: account, host, role and keys for Snowflake, Databricks, BigQuery, Redshift, Synapse and Fabric.

15 min read

This guide is for the person who administers the warehouse. You collect a read-only identity and paste it into Connect a warehouse. exelens never needs table access, write access or an account-admin role.

Snowflake

Preferred auth is an RSA key pair on a service user. Official docs: account identifiers, key-pair authentication, network policies.

  1. 1

    Find the account identifier

    In Snowsight: Admin → Accounts, or read it from the URL. A locator looks like xy12345.us-east-1. An organization account looks like myorg-analytics. Paste that value into Account identifier — not the full *.snowflakecomputing.com URL.

  2. 2

    Create a reader role, warehouse and service user

    Sign in as SECURITYADMIN or SYSADMIN. Run the script from the connection wizard (placeholders <DATABASE>, <SCHEMA>, <VIEW>). It creates EXELENS_READER, a small warehouse with a resource monitor, and grants SELECT on views only.

  3. 3

    Generate an RSA key pair (preferred)

    Follow Snowflake’s key-pair guide. Put the public key on the user (RSA_PUBLIC_KEY in the script). Keep the private PEM for exelens — include the BEGIN / END lines. A passphrase is optional.

  4. 4

    Restrict the user to exelens IPs

    Copy the addresses under Data → Network allowlist into the network policy in the script, then attach it to the service user.

Field in exelensWhere to find it
Account identifierAdmin → Accounts, or the account part of the Snowsight URL
WarehouseThe dedicated warehouse from the script (for example EXELENS_WH)
Database / RoleDatabase that holds the views; role EXELENS_READER
User + private keyService user name and the PEM private key (key-pair auth)
User + passwordOnly if you cannot use a key pair

Databricks

Preferred auth is an OAuth machine-to-machine service principal. Official docs: workspace URL, SQL warehouse HTTP path, OAuth M2M, personal access tokens, Unity Catalog privileges, IP access lists.

  1. 1

    Copy the workspace host

    From the browser URL, take the host only: adb-1234567890123456.7.azuredatabricks.net or xxx.cloud.databricks.com. Do not include https:// or a path.

  2. 2

    Copy the SQL warehouse HTTP path

    SQL Warehouses → your small serverless warehouse → Connection details. The HTTP path looks like /sql/1.0/warehouses/<id>. Grant the principal CAN USE on that warehouse.

  3. 3

    Create a service principal (OAuth M2M)

    Account console → Service principals → add exelens-reader. Generate an OAuth secret. The UUID is the Client ID; the generated secret is the Client secret. Then grant USE CATALOG, USE SCHEMA and SELECT on each view in Unity Catalog (the wizard script).

  4. 4

    Allowlist IPs

    Workspace → Settings → IP access lists. Add the egress IPs from Data. A PAT is a fallback if you cannot create a service principal; it is tied to a person and expires.

Field in exelensWhere to find it
HostWorkspace hostname, no https://
HTTP pathSQL warehouse → Connection details
CatalogUnity Catalog name that holds the views
Client ID / secretService principal UUID and OAuth secret
TokenPAT, only if you are not using OAuth M2M

BigQuery

Preferred auth is Workload Identity Federation (no JSON key stored). Official docs: Workload Identity Federation, AWS provider, service account keys, BigQuery IAM roles.

  1. 1

    Note the project and location

    Project ID is on the Cloud Console home (not the display name). Location is the dataset region, for example US or europe-west1.

  2. 2

    Create a reader service account

    Grant roles/bigquery.jobUser on the project and roles/bigquery.dataViewer only on the datasets that hold the views you will import. Authorize those views to read their source datasets if the sources live elsewhere.

  3. 3

    Federation (recommended) or a JSON key

    For WIF, create a pool and an AWS provider that trusts the exelens AWS account (the wizard script). Download the client-library JSON and paste it into Workload identity federation config. The JSON-key alternative is a service-account key file — rotate it if it ever leaks.

Field in exelensWhere to find it
Project IDCloud Console project picker
LocationDataset region (US, EU, or a region id)
WIF config (JSON)Client-library config from the workload identity pool
Service account key (JSON)IAM → Service accounts → Keys (fallback)

Amazon Redshift

Preferred auth is a cross-account IAM role for the Data API. Official docs: Redshift Data API, roles for a third party (External ID).

  1. 1

    Identify the workgroup or cluster

    Serverless: the workgroup name. Provisioned: the cluster identifier. Also note the AWS region and the database name.

  2. 2

    Create a database user that can only SELECT views

    Run the wizard script: user exelens_reader, group with USAGE on the schema and SELECT on each view. Password auth is a fallback and needs host + port.

  3. 3

    Create the IAM role exelens will assume

    Trust the exelens AWS account with the External ID from the wizard. Allow redshift-data:ExecuteStatement, DescribeStatement, GetStatementResult and redshift:GetClusterCredentials scoped to that workgroup or cluster. Paste the role ARN, External ID and database user name.

Field in exelensWhere to find it
Database / RegionTarget database and the AWS region of the workgroup or cluster
Workgroup or Cluster IDServerless workgroup name, or provisioned cluster id
Role ARN / External ID / DB userCross-account role and the Redshift user it maps to
Host / port / passwordOnly for database-user auth

Azure Synapse and Microsoft Fabric

Both use a Microsoft Entra service principal mapped to a database user. Official docs: create a service principal, Synapse IP firewall, Fabric service-principal access.

  1. 1

    Create an Entra app registration

    Microsoft Entra ID → App registrations → New. Note the Directory (tenant) ID and Application (client) ID. Under Certificates & secrets, create a client secret and copy it once.

  2. 2

    Map it to a database user and grant SELECT on views

    In the Synapse dedicated pool or Fabric warehouse, run the wizard script (CREATE USER [exelens-reader] FROM EXTERNAL PROVIDER and GRANT SELECT on each view). In Fabric, also share the warehouse with the app as Viewer or Read.

  3. 3

    Copy host, port and database, then allowlist IPs

    Host is the SQL endpoint (Synapse: *.sql.azuresynapse.net; Fabric: the warehouse SQL connection string host). Default port is 1433. Add the egress IPs to the Synapse firewall or Fabric network rules.

Field in exelensWhere to find it
Host / port / databaseSQL endpoint, 1433 unless you changed it, database or warehouse name
Tenant ID / Client ID / Client secretEntra app registration
SQL user / passwordSynapse only, if you cannot use Entra