Security#

Starburst control plane provides authentication, TLS, provisioning of users and groups, and authorization options for securing access to your clusters.

In managed mode, control plane authenticates the users of all your clusters, provisions users and groups, and manages access with Starburst access control. In standalone mode, each cluster keeps its own authentication and access control. For the modes, see Deployment modes.

To provision users and groups, see Synchronize users and groups with LDAP and Provision users and groups with SCIM. To let control plane authenticate to your clusters, see Configure cluster authentication.

Best practices#

  • Always enable TLS for production deployments.

  • Generate secrets with at least 256 bits of entropy.

  • In standalone mode, make sure that the authentication signing secret is identical across control plane and all clusters: web-ui.shared-secret for password or insecure authentication, or http-server.authentication.oauth2.state-key for OAuth2. See Shared secrets.

  • Use environment variables or a secret management system to store secrets.

  • When using load balancer TLS termination, secure the network between the load balancer and control plane.