Secrets Management in Konnect
Secrets management in Konnect allows you to store secrets in centralized vaults, making it easier to manage security and governance policies.
Secrets can be part of the core gateway configuration,
or part of gateway configuration associated with APIs serviced by the gateway.
The most common types of secrets include:
- API keys
- Personal access tokens
- Credentials for databases
- Certain plugin fields, like
session_secret in the OIDC plugin
You can use vaults to safely store and retrieve secrets used in Kong Gateway
deployments, improving the fundamental security of your applications.
In the configuration, you can reference the secrets stored in vaults as variables instead
of displaying the actual value of the secret in plaintext. This way, the Konnect
platform never stores sensitive credentials.
Vaults interface in Konnect
Figure 1: Overview page for all vaults configured for a runtime group.
||Vaults menu link
||Main link to the vaults configuration for a runtime group. Appears when you select a runtime group.
||Click the Add vault button to set up any supported Konnect vault backend.
||Select a vault entry to open the configuration page for the particular vault. On each vault’s configuration page, you can edit or delete the vault, or copy the entire configuration as JSON.
||The vault’s UUID.
||Vault action menu
||From this menu, you can view, edit, or delete a vault’s configuration.
Vaults have several use cases:
- Storing secrets securely
- Managing access to secrets with fine-grained policies
- Applying internal security policies
- Automating secret rotation
- Auditing secrets usage
- Encryption of secrets at rest
Konnect does not:
- Store credentials to access the vault itself.
You must provide those credentials to the Kong Gateway data plane directly.
- Update or modify the secrets in 3rd party vaults.
Vaults are configurable per runtime group. You can’t use the same vault across
multiple runtime groups.
Supported vaults in Konnect
Konnect supports the following vault backends:
- AWS Secrets Manager
- HashiCorp Vault
- GCP Secret Manager
- Environment variables
You can manage all of these vaults through the Runtime Manager or with decK.
Check out the example use case for storing certificates in a vault.
For detailed vault configuration references and guides, see the Kong Gateway