Configure Starburst Integration v2.0
This page details how to install the Starburst integration v2.0.
A valid Starburst Enterprise license.
1 - Enable the Integration
- Click the App Settings icon in the left sidebar.
- Click the Integrations tab.
- Click Add Native Integration and select Trino from the Native Integration Type dropdown menu.
- Click Save.
2 - Configure the Immuta System Access Control Plugin in Starburst
Default Configuration Property Values
If you use the default property values in the configuration file described in this section,
- you will give users read and write access to tables that are not registered in Immuta and
- results for
SHOWqueries will not be filtered on table metadata.
These default settings help ensure that a new Starburst integration installation is minimally disruptive for existing Starburst deployments, allowing you to then add Immuta data sources and update configuration to enforce more controls as you see fit.
access-control.config-files property can be configured to allow Immuta to work with
existing Starburst installations that have already configured an access control provider. For example, if
the Starburst integration v2.0 is configured to allow users write access to tables that are not protected
by Immuta, you can still lock down write access for specific non-Immuta tables using an additional access
Create the Immuta access control configuration file in the Starburst configuration directory (
/etc/starburst/immuta-access-control.propertiesfor Docker installations or
<starburst_install_directory>/etc/immuta-access-control.propertiesfor standalone installations).
The table below describes the properties that can be set during configuration.
Property Starburst version Required or optional Description
392 and newer Required This property enables the integration. Both the Starburst integration and the Starburst integration v2.0 can be enabled at the same time. The
immuta.allowed.non.immuta.datasource.operationsproperty (explained below) must contain at least READ when both integrations are enabled.
392 and newer Optional Starburst allows you to enable multiple system access control providers at the same time. To do so, add providers to this property as comma-separated values. Immuta has tested the Immuta system access control provider alongside the Starburst built-in access control system. This approach allows Immuta to work with existing Starburst installations that have already configured an access control provider. Immuta does not manage all permissions in Starburst and will default to allowing access to anything Immuta does not manage so that the Starburst integration v2.0 complements existing controls. For example, if the Starburst integration v2.0 is configured to allow users write access to tables that are not protected by Immuta, you can still lock down write access for specific non-Immuta tables using an additional access control provider.
413 and newer Optional This property defines a comma-separated list of allowed operations for users on Immuta data sources they are subscribed to:
WRITE. When set to
WRITE, all users subscribed to data sources are allowed read and write operations to data source schemas and tables. By default, this property is set to
READ, which blocks write operations on data source tables and schemas.
392 and newer Optional This property defines a comma-separated list of allowed operations users will have on tables not registered as Immuta data sources. If this property is left empty, users will not get access to any tables outside Immuta. By default, this property is set to
392 and newer Required This should be set to the Immuta API key displayed when enabling the integration on the app settings page.
392 and newer Optional This property allows you to specify a path to your CA file.
392 and newer Optional Amount of time in seconds for which a user's specific representation of an Immuta data source will be cached for. Changing this will impact how quickly policy changes are reflected for users actively querying Starburst. By default, cache expires after 30 seconds.
392 and newer Optional Amount of time in seconds for which a user's available Immuta data sources will be cached for. Changing this will impact how quickly data sources will be available due to changing projects or subscriptions. By default, cache expires after 30 seconds.
392 and newer Required The protocol and fully qualified domain name (FQDN) for the Immuta instance used by Starburst (for example,
https://my.immuta.instance.io). This should be set to the endpoint displayed when enabling the integration on the app settings page.
392 and newer Optional When set to false, Immuta won't filter unallowed table metadata, which helps ensure Immuta remains noninvasive and performant. If this property is set to true, running
show catalogs, for example, will reflect what that user has access to instead of returning all catalogs. By default, this property is set to false.
420 and newer Required if
immuta.user.adminis not set
This property identifies the Starburst group that is the Immuta administrator. The users in this group will not have Immuta policies applied to them. Therefore, data sources should be created by users in this group so that they have access to everything. Note that you must escape regex special characters (for example,
392 and newer Required if
immuta.group.adminis not set
This property identifies the Starburst user who is an Immuta administrator (for example,
immuta.user.admin=immuta_system_account). This user will not have Immuta policies applied to them because this account will run the subqueries. Therefore, data sources should be created by this user so that they have access to everything. Note that you must escape regex special characters (for example,
Enable the Immuta access control plugin in Starburst's configuration file (
/etc/starburst/config.propertiesfor Docker installations or
<starburst_install_directory>/etc/config.propertiesfor standalone installations). For example,
Example Immuta System Access Control Configuration
# Enable the Immuta System Access Control (v2) implementation. access-control.name=immuta # The Immuta endpoint that was displayed when enabling the Starburst integration in Immuta. immuta.endpoint=http://service.immuta.com:3000 # The Immuta API key that was displayed when enabling the Starburst integration in Immuta. immuta.apikey=45jdljfkoe82b13eccfb9c # The administrator user regex. Starburst usernames matching this regex will not be subject to # Immuta policies. This regex should match the user name provided at Immuta data source # registration. immuta.user.admin=immuta_system_account # Optional argument (default is shown). # A CSV list of operations allowed on schemas/tables not registered as Immuta data sources. # Set to empty to allow no operations on non-Immuta data sources. immuta.allowed.non.immuta.datasource.operations=READ,WRITE # Optional argument (default is shown). # Controls table metadata filtering for inaccessible tables. # - When this property is enabled and non-Immuta reads are also enabled, a user performing # 'show catalogs/schemas/tables' will not see metadata for a table that is registered as # an Immuta data source but the user does not have access to through Immuta. # - When this property is enabled and non-Immuta reads and writes are disabled, a user # performing 'show catalogs/schemas/tables' will only see metadata for tables that the # user has access to through Immuta. # - When this property is disabled, a user performing 'show catalogs/schemas/tables' can see # all metadata. immuta.filter.unallowed.table.metadata=false
3 - Add Starburst Users to Immuta
- Configure your external IAM to add users to Immuta.
- Map their Starburst usernames when configuring your IAM
(or map usernames manually) to Immuta.
- All Starburst users must map to Immuta users or match the
immuta.user.adminregex configured on the cluster, and their Starburst username must be mapped to Immuta so they can query policy-enforced data.
- A user impersonating a different user in Starburst requires the IMPERSONATE_USER permission in Immuta.
Both users must be mapped to an Immuta user, or the querying user must match the configured
- All Starburst users must map to Immuta users or match the