Encrypt database secrets using Azure Key Vault
You can use an encryption key from Azure Key Vault to encrypt secrets in the Grafana database.
- An Azure account with permission to view and create Key Vault keys and programmatic credentials to access those keys
- Access to the Grafana configuration file
Create a key in the Key Vault with the name that you want by using RSA as the type and
2048as the size with encrypt and decrypt permissions.
Register an application and generate a client secret for it.
Assign a Key Vault access policy for the key vault that you created:
In the Key Permissions section, set encrypt and decrypt permissions, and click Save.
From within Grafana, turn on envelope encryption.
Add your Azure Key Vault details to the Grafana configuration file; depending on your operating system, is usually named
a. Add a new section to the configuration file, with a name in the format of
<KEY-NAME>is any name that uniquely identifies this key among other provider keys.
b. Fill in the section with the following values:
tenant_id: the Directory ID (tenant) from the application that you registered.
client_id: the Application ID (client) from the application that you registered.
client_secret: the VALUE of the secret that you generated in your app. (Don’t use the Secret ID).
key_id: the key name that you created in the key vault.
vault_uri: the URL of your key vault.
An example of an Azure Key Vault provider section in the
grafana.inifile is as follows:
# Azure Key Vault provider setup ;[security.encryption.azurekv.example-encryption-key] # Azure Application directory ID (tenant) tenant_id = 1234abcd-12ab-34cd-56ef-1234567890ab # Azure Application application ID (client). client_id = 1356dfgh-12ab-34cd-56ef-3322114455cc # Azure Application client secret. client_secret = FbE4X~4Jq45ERKxx823Aheb9plBjQqHHe81Sc # Azure Key Vault key name. key_id = mysecretkey # Azure Key Vault uri. vault_uri = https://my-vault-name.vault.azure.net
[security]section of the
grafana.iniconfiguration file with the new Encryption Provider key that you created:
[security] # previous encryption key, used for legacy alerts, decrypting existing secrets or used as default provider when external providers are not configured secret_key = AaaaAaaa # encryption provider key in the format <PROVIDER>.<KEY-NAME> encryption_provider = azurekv.example-encryption-key # list of configured key providers, space separated available_encryption_providers = azurekv.example-encryption-key
> Note: The encryption key stored in the
secret_keyfield is still used by Grafana’s legacy alerting system to encrypt secrets. Do not change or remove that value.
(Optional) From the command line and the root directory of Grafana Enterprise, re-encrypt all of the secrets within the Grafana database with the new key using the following command:
grafana-cli admin secrets-migration re-encrypt
If you do not re-encrypt existing secrets, then they will remain encrypted by the previous encryption key. Users will still be able to access them.
> Note: This process could take a few minutes to complete, depending on the number of secrets (such as data sources or alert notification channels) in your database. Users might experience errors while this process is running, and alert notifications might not be sent.
> Note: If you are updating this encryption key during the initial setup of Grafana before any data sources, alert notification channels, or dashboards have been created, then this step is not necessary because there are no secrets in Grafana to migrate.
Related Grafana resources
Unify your data with Grafana plugins: Datadog, Splunk, MongoDB, and more
In this webinar, learn how to leverage Grafana's plugin ecosystem for access to 80+ data sources, including plugins for Datadog, Splunk, MongoDB, and more.
Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.