​Enterprise ​Edition ​Configuration

This section describes how to configure Kestra Enterprise Edition.

Kestra Enterprise Edition offers many enhancements over the Open Source Edition, adding authentication, security, audit logs, and more. Here are some of the features available in the Enterprise Edition:

• Multi-Tenancy
• Audit Logs
• Authentication
• SSO
• RBAC
• Secrets Manager
• Namespace Management
• Worker Groups
• Worker Isolation

Enterprise Edition license

To use Kestra Enterprise Edition, you will need a valid license. Our sales team should have provided this license to you; if it's not the case, please reach out to them at [email protected].

The license is set up using two configuration properties: the id and the key.

• kestra.ee.license.id: should hold the license identifier.
• kestra.ee.license.key: should hold the license key.

When you launch Kestra Enterprise Edition, it will check the license and display the validation step in the log.

SuperAdmin User from configuration

The current most powerful user in Kestra is the SuperAdmin

For setup facilities, you can create a SuperAdmin user from the configuration file.

The super-admin required three properties :

• kestra.security.super-admin.username: the username of the super-admin
• kestra.security.super-admin.password: the password of the super-admin
• kestra.security.super-admin.tenantAdminAccess: a list of tenants that the super-admin can access
  • This property can be omit if you do not use multitenancy
  • If a Tenant does not exists, it will be created
  • At each startup, this user is checked and if the list of access has been modified new accesses can be created, but none will be removed

kestra:
  security:
    super-admin:
      username: <username>
      password: <password>
      tenantAdminAccess:
        - <optional>