Getting Started with Starburst (Trino)
Last updated
Was this helpful?
Last updated
Was this helpful?
The how-to guides linked on this page illustrate how to integrate Starburst (Trino) with Immuta. See the for information about the Starburst (Trino) integration.
These guides provide instructions on getting your data set up in Immuta.
: Install the Immuta Starburst (Trino) plugin in Starburst or Trino so that policies can be applied to data objects.
: This will register your data objects into Immuta and allow you to start dictating access through global policies.
: Use domains to segment your data and assign responsibilities to the appropriate team members. These domains will then be used in policies, audit, and sensitive data discovery.
These guides provide instructions on getting your users set up in Immuta.
: Bring the IAM your organization already uses and allow Immuta to register your users for you.
: Ensure the user IDs in Immuta, Starburst (Trino), and your IAM are aligned so that the right policies impact the right users.
These guides provide instructions on getting your data metadata set up in Immuta.
: Bring the external catalog your organization already uses and allow Immuta to continually sync your tags with your data sources for you.
: Sensitive data discovery (SDD) allows you to automate data tagging using identifiers that detect certain data patterns.
These guides provide instructions on using the Governance app for the first time.
: Once you add your data metadata to Immuta, you can immediately create policies that utilize your tags and apply to your tables. Subscription policies can be created to dictate access to data sources.
: Data metadata can also be used to create data policies that apply to data sources as they are registered in Immuta. Data policies dictate what data a user can see once they are granted access to a data source. Using catalog and SDD tags you can create proactive policies, knowing that they will apply to data sources as they are added to Immuta with the automated tagging.
: Once you have your data sources and users, and policies granting them access, you can set up audit export. This will export the audit logs from user queries, policy changes, and tagging updates.