Getting Started with Starburst (Trino)

The how-to guides linked on this page illustrate how to integrate Starburst (Trino) with Immuta and gain value from the Immuta modules: Detect, Discover, and Secure.

Configure your Starburst (Trino) integration

Configuring a Starburst (Trino) integration is required for Secure. These guides provide information on the recommended features to enable with Starburst (Trino).

1. Configure your Starburst (Trino) integration.

2. Select None as your default subscription policy.

3. Integrate an IAM with Immuta.

4. Map external user IDs from Starburst (Trino) to Immuta.

Register metadata

These guides provide instructions for organizing your Starburst (Trino) data to align with your governance structure.

1. Register Starburst (Trino) data in Immuta as data sources.

2. Recommended: Organize your data sources into domains and assign domain permissions to accountable teams.

Detect your user activity

These guides provide instructions for auditing and detecting your users' activity, or see the Detect use case for a comprehensive guide on the benefits of these features and other recommendations.

1. Set up audit export to S3 or ADLS Gen2 for your Starburst (Trino) audit logs.

2. View the Detect dashboards to see the activity of your registered users on registered tables.

Discover your data

Public preview: Native SDD for Starburst (Trino) is currently in public preview and available to all accounts.

These guides provide instructions for discovering, classifying, and tagging your data.

1. Enable sensitive data discovery (SDD).

2. Register a subset of your tables to configure and validate SDD.

3. Configure SDD to discover entities of interest for your policy needs.

4. Validate that the SDD tags are applied correctly.

5. Register your remaining tables at the schema level with schema monitoring turned on.

6. Implement classification to categorize and tag sensitive data.

Secure your data

These guides provide instructions for configuring and securing your data with governance policies, or see the Secure use cases for a comprehensive guide on creating policies to fit your organization's use case.

1. Create a global subscription policy.

2. Create a global data policy.

3. Validate the policies. You do not have to validate every policy you create in Immuta; instead, examine a few to validate the behavior you expect to see.

4. Once all Immuta policies are in place, remove or alter old permissions and revoke access to the ungoverned tables.