Skip to content

You are viewing documentation for Immuta version 2022.1.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Configure Starburst Integration

Audience: System Administrators

Content Summary: This page details how to install the Starburst integration. Starburst is only available with certain licenses. Please see your Immuta representative for more information.

Prerequisites: The Starburst ODBC driver must be uploaded on the App Settings page.

Installation Method

This installation method is only available to users on Starburst Enterprise. If you are using any other form of Trino, please see the other installation method.

1 - Enable Native Starburst

  1. Click the App Settings icon in the left sidebar.
  2. Click Enable in the Trino Integration section.

    Dynamic Trino Enable

  3. Click Save.

2 - Configure the Immuta Connector in Starburst

  1. Create a configuration file immuta.properties with the following contents in the etc/catalog folder:

    connector.name=immuta
    immuta.endpoint=https://your-immuta-url.com/
    immuta.apikey=<your-api-key>
    

For more details, see Starburst's Event Listener documentation.

3 - Configure the Event Listener

  1. Create an etc/event-listener.properties file in the same etc/catalog folder.
  2. Copy the Event Listener Configuration items from the App Settings page and paste it in the event-listener.properties file:

    Dynamic Trino Event Listener

For more details, see Starburst's Event Listener documentation.

4 - Configure Starburst to Block Access

Best Practice: Give Users read-only Access to Immuta Catalog

Give users read-only access to the Immuta catalog. This will prevent users from describing the views, which in turn prevents them from seeing secrets involved in some masking policies.

Follow Starburst's System Access Control documentation to configure Starburst to block access to any catalog that is not Immuta so that all user access has policies enacted on it.