Setup for Access Management for Starburst Trino¶
Configure¶
Perform following steps to configure Starburst Trino plugin:
-
SSH into the instance where Privacera Manager is installed.
-
Run the following command to navigate to the
/configdirectory and copy yml files: - Modify the following properties:
- Update the
vars.trino.opensource.ymlfile as follows:
- Update the
-
After configuring the properties, start the connector by executing the following instructions:
Run the following command to run the post install steps:
Copy Privacera Trino Plugin Configuration Files¶
- Run the following command to copy required configuration files:
Create entrypoint.sh Script¶
-
Run the following command to create and edit
entrypoint.shfile: -
Add the following content in the
entrypoint.shfile:
Create Dockerfile¶
Create the file in the same directory as the entrypoint.sh script.
-
Run the following command to create and edit the Dockerfile:
-
Add the content for your Starburst Enterprise version to the Dockerfile:
Dockerfile for Starburst Enterprise 479-e.13 and earlier
Dockerfile for Starburst Enterprise 479-e.14 and later
Enable Trino Application¶
- In PrivaceraCloud, navigate to Settings -> Applications.
- On the Applications screen, select Trino.
- Enter the application Name and Click Save. You can choose any name, for example,
Trino. - Enable the Access Management option with toggle button.
- Click on Save button.
Create Entrypoint.sh Script¶
-
Run the following command to create and edit entrypoint.sh file:
-
Add the following content in the entrypoint.sh file:
Create Dockerfile¶
Create the file in the same location as the entrypoint.sh script.
-
Run the following command to create and edit Dockerfile:
-
Add the following content in the Dockerfile:
Configure the connector in Runtime and download it as a bundle. Unpack the bundle on the workstation that builds the Starburst Trino image. The image carries the setup script that installs the plugin when the coordinator starts.
Note
Runtime support for this connector is available on Self-Managed and D2P planes only.
Configure the Starburst Trino connector¶
-
In the portal, open the runtime plane and go to the Connector tab. If no runtime plane exists yet, see Getting Started with Runtime Plane.
-
Add the Trino connector, select Starburst Enterprise as the distribution, and set the fields it asks for:
Field Definition Example Trino distribution Engine this cluster runs. Selects the install and configuration paths below. Starburst EnterpriseStarburst install directory Where the engine is installed. The plugin is linked into plugin/under this path./usr/lib/starburstStarburst configuration directory Where the engine reads its configuration. The Ranger XML is written to ranger-conf/under this path./etc/starburstEnable debug logging Off by default. Turning it on reveals the three log levels below. false -
Logging - only if Enable debug logging is on. For the fields and how to verify the logs afterwards, see Enable Debug Logs.
-
Custom Properties - optional. Any key and value added here is written into the plugin's configuration, for settings this form does not expose. The key is the property name exactly as it appears there.
For example, plugin metrics are off by default and the form does not expose them, so a deployment that scrapes them with Prometheus sets:
Key Value Default TRINO_PLUGIN_METRICS_ENABLEtruefalseTRINO_PLUGIN_METRICS_PROMETHEUS_LISTENER_ENABLEtruefalseTRINO_PLUGIN_METRICS_PROMETHEUS_LISTENER_PORT90909090The key must match its name in
install.propertiesexactly. A name that is not already in that file is appended as a line nothing reads. -
Advanced Configuration - optional. Options this form does not carry, such as a custom service repository or deny policy dominance, are set through Custom Properties. Each page under Advanced Configuration has a Runtime tab saying which applies.
-
Save the configuration, then download the connector bundle.
The bundle contents depend on the plane, because certificates are shipped only where the plugin needs them:
Plane Bundle contents Self-Managed trust3ai_trino_plugin_<connector>_<version>.shandprivacera_trino_plugin_conf.zipD2P trust3ai_trino_plugin_<connector>_<version>.shonlyOn D2P the plugin reaches Ranger and the audit server through the API server using the plane API key, so no client certificates are involved.
Unpack the bundle¶
Perform these steps on the workstation where the Starburst Trino image is built.
-
Create the build folder and unpack the bundle into a
trust3ai_plugin/sub-folder. TheDockerfilecopies that whole folder, so the same file works whether or not the plane ships a configuration zip. -
Confirm the contents. The
Dockerfileandentrypoint.shcreated below belong besidetrust3ai_plugin/, not inside it.Bash On a D2P plane the zip is absent and only the script is listed. That is expected - the
Dockerfilecopies whatever the folder holds. -
Rename the setup script to a fixed name. The downloaded name carries the connector and version, so renaming it keeps the
Dockerfileandentrypoint.shunchanged from one bundle to the next.
Create Entrypoint.sh Script¶
Create entrypoint.sh in the same folder, with the following content.
Create Dockerfile¶
Create the file in the same directory as the entrypoint.sh script.
Build the Docker Image¶
- Run the following command to build the Docker image:
Bash
Push the Docker Image to the Remote HUB¶
- Use your internal HUB to publish the image.
Create Starburst License File¶
- Create a file containing Starburst license details, add the license key and save the file.
Create a Namespace¶
- Run the following command to create a namespace.
Bash
Create Kubernetes secret¶
Applicable only for PrivaceraCloud and Data Plane deployments. Not required for Runtime (Self-Managed or D2P) deployments.
- Obtain the
PCLOUD_PLUGIN_SCRIPT_URLfrom PrivaceraCloud → Settings → API Keys:- Click the ℹ️ icon next to an existing key (or generate a new key first) to open API Key Info.
- Locate the Plugin Setup Script row and click COPY URL.
- The copied URL contains the placeholder
__API_KEY__. Replace it with the actual API key value — the one shown once in the Generated API Key dialog when the key was created. If you no longer have that value, generate a new API key and use it here.
- Create a Kubernetes secret for the Privacera plugin setup script URL. Run the following command:
Create Starburst License Secret¶
- Run the following command to create a secret for Starburst license:
Bash
Create Docker Image Secret¶
- To create an image secret, run the following command:
Verify the Secrets¶
- To verify the secret, run the following command:
Bash
Create .yaml Deployment File to Override the Default Values¶
-
Run the following command to create and edit the values.yaml file:
-
Add the following content in the values.yaml file based on deployment environment:
-
(Optional) To enable Data Products use the following values.yaml
Note
Access control for Data Products is supported in Starburst Trino version 468 and later.
values.yaml
Install Starburst Trino on Kubernetes Cluster¶
- Upgrade an existing Helm release or install it if not present using the chart, version, and values file.
- Prev topic: Connector Guide
- Next topic: Advanced Configuration