Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
🔑

Secrets manager

Updated 2026-11-20
On this page

Secrets manager

The secrets manager safely stores passwords, API keys, TLS material and other sensitive values in a hardened vault, controls who can read each one, and can generate strong secrets for you on demand.

Every secret is stored encrypted in the secure secrets service and is only ever returned to callers you have explicitly authorized. The console never shows a secret's value in a list; you must open the secret to reveal its payload, and access can be narrowed further with a per-secret access control list (ACL).

Secrets carry a type (for example passphrase, symmetric key, certificate or opaque blob), an optional algorithm and an optional expiration date. Related secrets can be grouped into containers so an application can consume a coherent set at once, such as a certificate together with its private key.

Screenshot — The Security > Secrets vault listing secrets with their type, status, algorithm and expiration
The Security > Secrets vault listing secrets with their type, status, algorithm and expiration

Key concepts

Secret — A single encrypted value (password, key, certificate) with a name, type and optional expiration.

Payload — The actual secret value. It is written once and read only through an authorized reveal.

Container — A named group of related secrets that an application or load balancer consumes together.

ACL — The per-secret access control list that decides which users or applications may read it.

Consumer — A service (such as a load balancer) that references a container and is listed against it.

Rotation — Replacing a secret's value with a new one while keeping the same name and references.

Before you start

  • You are working in the project that should own the secret.
  • You have the value to store, or you plan to generate one.
  • For certificate secrets, the certificate and its private key.

Step by step

  1. Open the vault

    Go to Security and open Secrets. The table shows each secret's name, type, status, algorithm and expiration.

    Screenshot — The Secrets vault with the search box and type filter
    The Secrets vault with the search box and type filter
  2. Create or generate a secret
    • Choose Create secret. On the Manual entry tab, give it a name and type, then paste the value or upload a file.
    • Or switch to the Generate tab to have the platform produce a strong random value (a passphrase, or a symmetric key with a chosen algorithm and key size).
    Screenshot — The Create secret dialog with the Manual entry and Generate tabs
    The Create secret dialog with the Manual entry and Generate tabs
  3. Copy a generated value now

    When you generate a secret, its value is shown once in a dialog. Copy it before closing, then store it wherever the consuming app expects it.

    Screenshot — The generated-secret confirmation showing the value to copy
    The generated-secret confirmation showing the value to copy
  4. Group related secrets

    Open Manage containers to create a container and add the secrets that belong together, for example a certificate and its private key.

    Screenshot — The container manager with member secrets
    The container manager with member secrets
  5. Restrict access

    Edit the secret's ACL so only the users or application credentials that truly need it can read the payload.

  6. Rotate or delete

    Use the row actions to reveal, rotate or delete a secret. Rotation is available for passphrase, symmetric and private-key secrets; certificate secrets have a dedicated certificate rotation.

Examples

Read a secret's value from a script (Patrii CLI)
# List secrets, then fetch one payload by ID
patrii secret list
patrii secret get <secret-id> --output-file db-password.txt
Generate a strong passphrase from the CLI
patrii secret generate \
  --name prod-db-password \
  --type passphrase \
  --length 32
Store a secret with Terraform
resource "patrii_secret" "db_password" {
  name                 = "prod-db-password"
  secret_type          = "passphrase"
  payload              = var.db_password
  payload_content_type = "text/plain"
}

Limits & specifications

Secret types you can store:

TypeTypical use
passphrasePasswords and human-style secrets; can be generated and rotated.
symmetricSymmetric encryption keys (for example AES) with a chosen key size.
public / privateThe two halves of an asymmetric key pair (RSA, ECDSA, EdDSA).
certificateTLS certificates, managed and rotated on their own; consumable by load balancers.
opaqueAny arbitrary blob the platform does not need to interpret.

Best practices

  • Prefer generated secrets over hand-typed ones for anything machine-to-machine.
  • Give each secret a clear name and set an expiration so stale material is easy to spot.
  • Grant read access with an ACL to the smallest set of users or application credentials that need it.
  • Group a certificate with its private key in a container so consumers reference one object.
  • Rotate secrets on a schedule and immediately after any suspected exposure.

FAQ

Can I see a secret's value in the list?
No. The list only shows metadata. You must open a secret and reveal it, and a generated value is shown once at creation. Store it somewhere safe at that moment.
What does the Used In column mean?
It shows the containers a secret belongs to and any service consuming them, for example a load balancer that terminates TLS with a certificate container. Delete those consumers before deleting the secret.
Why can't I delete a secret?
A secret that is still referenced by a container or an active consumer cannot be removed. Detach it from the container or remove the consumer first, then delete it.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us