KMS integration on Grafana Labs

Azure Key Vault

Fri, 07 Mar 2025 11:34:44 +0100

Using Azure Key Vault to encrypt database secrets

You can use an encryption key from Azure Key Vault to encrypt secrets in the Grafana database.

Prerequisites:

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 vault.
Create a key in the Key Vault with the name that you want by using RSA as the type and 2048 as 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 grafana.ini:

a. Add a new section to the configuration file, with a name in the format of [security.encryption.azurekv.<KEY-NAME>], where <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.ini file 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
```

Update the [security] section of the grafana.ini configuration 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_key field is still used by Grafana’s legacy alerting system to encrypt secrets. Do not change or remove that value.

Restart Grafana.
(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.

AMS KMS

Fri, 07 Mar 2025 11:34:44 +0100

Using AWS KMS to encrypt database secrets

You can use an encryption key from AWS Key Management Service to encrypt secrets in the Grafana database.

Prerequisites:

An AWS account with permission to view and create KMS keys and programmatic credentials to access those keys
Access to the Grafana configuration file

Create a symmetric API key either from the AWS Management Console or by using the AWS KMS API.

For detailed instructions, refer to Creating keys.
Retrieve the Key ID.

In AWS terms, this can be a key ID, a key ARN (Amazon Resource Name), an alias name, or an alias ARN. For more information about how to retrieve a key ID from AWS, refer to Finding the key ID and key ARN.
Create a programmatic credential (access key ID and secret access key), which has permission to view the key that you created.

In AWS, you can control access to your KMS keys by using key policies, IAM policies, and grants. You can also create temporary credentials, which must provide a session token along with an access key ID and a secret access key.
From within Grafana, turn on envelope encryption.

Add your AWS KMS details to the Grafana configuration file; depending on your operating system, it is usually named grafana.ini:

a. Add a new section to the configuration file, with a name in the format of [security.encryption.awskms.<KEY-NAME>], where <KEY-NAME> is any name that uniquely identifies this key among other provider keys.

b. Fill in the section with the following values:

key_id: a reference to a key stored in the KMS. This can be a key ID, a key Amazon Resource Name (ARN), an alias name, or an alias ARN. If you are using an alias, use the prefix alias/. To specify a KMS key in a different AWS account, use its ARN or alias. For more information about how to retrieve a key ID from AWS, refer to Finding the key ID and key ARN.

`key_id` option	Example value
Key ID	`1234abcd-12ab-34cd-56ef-1234567890ab`
Key ARN	`arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab`
Alias name	`alias/ExampleAlias`
Alias ARN	`arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias`

access_key_id: The AWS Access Key ID that you previously generated.
secret_access_key: The AWS Secret Access Key you previously generated.
region: The AWS region where you created the KMS key. The region is contained in the key’s ARN. For example: arn:aws:kms:*us-east-2*:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab

An example of an AWS KMS provider section in the grafana.ini file is as follows:

# AWS key management service provider setup
;[security.encryption.awskms.example-encryption-key]
# Reference to a KMS key - either key ID, key ARN, alias name, or ARN
;key_id = 1234abcd-12ab-34cd-56ef-1234567890ab
# AWS access key ID
;access_key_id = AKIAIOSFODNN7EXAMPLE
# AWS secret access key
;secret_access_key = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
# AWS region, for example eu-north-1
;region = eu-north-1

Update the [security] section of the grafana.ini configuration 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 = awskms.example-encryption-key
# list of configured key providers, space separated
available_encryption_providers = awskms.example-encryption-key
```
> Note: The encryption key that is stored in the secret_key field is still used by Grafana’s legacy alerting system to encrypt secrets, for decrypting existing secrets, or it is used as the default provider when external providers are not configured. Do not change or remove that value when adding a new KMS provider.
Restart Grafana.
(Optional) From the command line and the root directory of Grafana, 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.