Starburst/Trino Integration Prerequisite Checklist

This page offers a prerequisite checklist focused on customer's Starburst/Trino deployment that would help answer questions relating to Immuta's Starburst integration

Deployment Pattern

Starburst and/or Trino requires initially one of below deployment patterns. Which one is yours?

  1. On-Premises: Do you have a self managed on-premises Starburst/Trino deployment?

  2. Cloud: Which Cloud Provider (AWS, Azure, GCP or Red Hat OpenShift) are you using?

  3. Kubernetes: Do you use kubernetes or single node docker based deployment?

  4. Hybrid: Combine on-premises and cloud deployments for flexibility. What is your deployment pattern?

Networking Infrastructure

  • How many different Starburst/Trino clusters you have?

  • Are you segregating workloads by having separate Starburst clusters or separate Starburst catalogs?

  • Do you use PrivateLink? If so, is it cross-region or only single region? Details are on this link.

Access Control System

  • Do you have an existing access control system deployed on your Starburst/Trino cluster(s)?

  • If yes,

    • Do you use Ranger?

    • Do you use Starburst BIAC?

    • Do you use Trino file based access control?

    • Do you use any other access control system within your existing deployment?

User Authentication and Cluster Security

Immuta supports and adheres with most of the authentication methods but there may be some edge cases.

Immuta Configuration Specifics

Last updated