Frequently Asked Questions: Kestra Cloud and Enterprise

Frequently asked questions about the Cloud and Enterprise Edition of Kestra.

My session expires too quickly. Is there a way to change the session expiration time?

Add the following Micronaut setting to your Observability and Networking configuration to set the session expiration time to 10 hours:

    environment:
      KESTRA_CONFIGURATION: |
        micronaut:
          security:
            token:
              generator:
                access-token:
                  expiration: 36000
              cookie:
                cookie-max-age: 10h

On Kestra Cloud, contact support to change this setting.

How do I configure Kestra with my license details?

Kestra Enterprise Edition requires a valid license configured under kestra.ee.license. The license is unique to your organization. To get a license, contact the Sales team at sales@kestra.io.

The license uses three configuration properties: id, fingerprint, and key.

• kestra.ee.license.id: license identifier.
• kestra.ee.license.fingerprint: license authentication.
• kestra.ee.license.key: license key.

kestra:
  ee:
    license:
      id: <LICENSE ID>
      fingerprint: <LICENSE FINGERPRINT>
      key: |
        <LICENSE KEY>

Kestra validates the license on startup and logs the validation result.

When should I use Secrets vs Credentials?

Use Secrets when you need to store and reference sensitive values such as API keys, passwords, webhook URLs, or tokens in your flows and configuration. Secrets are the right choice when you want to inject a protected value with the secret() function or manage sensitive data centrally.

Use Credentials when a supported integration or plugin expects a reusable authentication object managed through the UI. Credentials are better suited to connection-level authentication that you want to define once and reuse across multiple flows.

In short: use Secrets for protected values, and use Credentials for managed authentication objects supported by Kestra integrations.