Skip to main content
Looking for our new Data Plane experience for connecting your data?
Hero Light

Connect to your data sources

  1. Navigate to the Connect application using the side navigation bar.
  2. Select your data source type.
To connect to a Postgres database, you’ll need:
  • Host: The server address of the Postgres instance.
  • Port: The port number where Postgres is running (default: 5432).
  • Database Name: The specific Postgres database to connect to.
  • User: The Postgres username.
  • Password: The corresponding password for the user.
  • Pool Size (optional): Number of active connections to maintain (default: 10).
  • Concurrency Limit (optional): Maximum number of concurrent queries.
  • Interval Limit (optional): Maximum number of operations in a time interval.
  • Interval Time (optional): Time interval in milliseconds (e.g., 1000 ms for 1 second).
  • Row-level-security (RLS) variable (optional): Variable name used in RLS policies (recommended: “app”).
  • Default row-level-security (RLS) value (optional): Default user value applied to RLS policies when in the Upsolve Hub.
Note on RLS: When using row-level security, ensure the database user for connection is not a superadmin, as RLS policies are bypassed by superusers.
To connect to Clickhouse, you’ll need:
  • Host: The Clickhouse server address (e.g., https://clickhouse-host).
  • Port: The port number (default: 8443 for HTTPS connections).
  • User: The Clickhouse username.
  • Password: The corresponding password for the user.
  • Database Name: The Clickhouse database to connect to.
  • Concurrency Limit (optional): Maximum number of simultaneous queries.
  • Interval Limit (optional): Maximum operations allowed during a time interval.
  • Interval Time (optional): Time interval in milliseconds.
  • Default Database (for Database Tenancy) (optional): When set, enables schema-based tenancy. The metadata will only include tables from this database, and it will be used as the default database for admin users and tenants without a schemaPreFilter configured.
To connect to Snowflake, you’ll need:
  • Account: The Snowflake account identifier (e.g., account_name.region.cloud_provider).
  • User: Your Snowflake username.
  • Password: Your Snowflake password.
  • Database Name: The specific Snowflake database to connect to.
To connect to a MySQL database:
  • Host: The MySQL server address.
  • Port: The port number (default: 3306).
  • Database Name: The MySQL database to connect to.
  • User: The MySQL username.
  • Password: The password for the user.
To connect to Microsoft SQL Server:
  • Host: The MS SQL server address.
  • Port: The port number (default: 1433).
  • Database Name: The MS SQL database to connect to.
  • User: The MS SQL username.
  • Password: The corresponding password for the user.
For AWS DynamoDB:
  • Region: The AWS region where DynamoDB is hosted (e.g., us-east-1).
  • AWS Access Key: The access key from your AWS IAM user.
  • AWS Secret Key: The secret key from your AWS IAM user.
To connect to Amazon Redshift:
  • Host: The Redshift cluster endpoint.
  • Port: The port number (default: 5439).
  • Database Name: The Redshift database to connect to.
  • User: The Redshift username.
  • Password: The password for the user.
To connect to TimescaleDB (Postgres with time-series capabilities):
  • Host: The server address where Timescale is running.
  • Port: The port number (default: 5432).
  • Database Name: The Timescale/Postgres database to connect to.
  • User: The database username.
  • Password: The password for the user.
To connect to Trino:
  • Host: The Trino coordinator server address.
  • Port: The port number (default: 8080 for HTTP, 443 for HTTPS).
  • User: The Trino username.
  • Password: The corresponding password for the user.
  • Catalog: The Trino catalog name (required).
  • Default Schema (optional): The default schema in the catalog (e.g. demo, public). Used for metadata and queries when no schema is specified.
To connect to AWS Athena, you’ll need:
  • Region: The AWS region hosting your Athena workgroup and Glue catalog (e.g., us-east-1).
  • Access Key ID: The access key ID from your AWS IAM user. Athena is IAM-authenticated, so this key pair is the equivalent of a username and password — the official Athena JDBC driver maps them the same way.
  • Secret Access Key: The matching secret key. Stored encrypted and never returned by the API.
  • S3 Output Location: The S3 URI Athena writes query results to, e.g. s3://my-bucket/athena-results/. Required — Athena stages every result set in S3 before it can be read back, so the IAM principal needs both read and write access to this prefix.
  • Database: The Glue database to introspect and query. Unlike other connection types this cannot be a comma-separated list, because Athena scopes information_schema to one database at a time.
  • Data Catalog (optional): The Glue data catalog to resolve tables against (default: AwsDataCatalog).
  • Workgroup (optional): The Athena workgroup to run queries in (default: primary).
The IAM policy attached to the key pair needs, at minimum: athena:StartQueryExecution, athena:GetQueryExecution and athena:GetQueryResults; glue:GetDatabase*, glue:GetTable* and glue:GetPartition* for the databases you expose; s3:GetObject/s3:PutObject on the output location; and s3:GetObject/s3:ListBucket on the buckets your tables read from.Notes on Athena:
  • Athena runs a Trino engine, so queries use Trino/Presto SQL — double-quoted identifiers, and date_trunc/date_format rather than their Postgres or MySQL equivalents.
  • Queries are billed per byte scanned. Selectable-column detection is therefore disabled for Athena connections: auto-detecting it would fire a COUNT per table on every metadata refresh.
  • Athena executions are asynchronous. Upsolve polls until the query completes and gives up after 120 seconds.
To connect to Supabase, use the following credentials and configuration steps:
  1. Create the execute_raw_sql Function: To enable secure execution of SQL queries, run the following SQL in your Supabase SQL editor:
  2. Set Up Credentials in Upsolve Hub: Use the following details to connect to your Supabase instance:
    • URL: The unique URL of your Supabase instance.
    • Anon Key: The public API key for accessing Supabase.
    • Service Key: The secret API key for accessing Supabase.
    You can find these details in your Supabase API settings.
For enterprise features, look for the 🔒 symbol. These features are available in our Enterprise plan. Please contact us for more information.
  1. Input the corresponding credentials for the data source.
Hero Light
  1. Click Save to see if connection is set up successfully.
Hero Light
You are now good to go to start building charts and creating dashboards. If you do not see the data source type you want to connect to in the Connect application, please raise a support ticket.