Skip to content

Commit 926e434

Browse files
authored
Merge pull request #109383 from dagiro/CMK1
CMK1
2 parents e307dad + b04c9a7 commit 926e434

File tree

1 file changed

+37
-1
lines changed

1 file changed

+37
-1
lines changed

articles/hdinsight/disk-encryption.md

Lines changed: 37 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 02/20/2020
1111

1212
# Customer-managed key disk encryption
1313

14-
Azure HDInsight supports customer-managed key encryption for data on managed disks and resource disks attached to HDInsight cluster virtual machines. This feature allows you to use Azure Key Vault to manage the encryption keys that secure data at rest on your HDInsight clusters.
14+
Azure HDInsight supports customer-managed key encryption for data on managed disks and resource disks attached to HDInsight cluster virtual machines. This feature allows you to use Azure Key Vault to manage the encryption keys that secure data at rest on your HDInsight clusters.
1515

1616
All managed disks in HDInsight are protected with Azure Storage Service Encryption (SSE). By default, the data on those disks is encrypted using Microsoft-managed keys. If you enable customer-managed keys for HDInsight, you provide the encryption keys for HDInsight to use and manage those keys using Azure Key Vault.
1717

@@ -142,6 +142,42 @@ az hdinsight rotate-disk-encryption-key \
142142
--resource-group MyResourceGroup
143143
```
144144

145+
## Azure Resource Manager templates
146+
147+
To use customer managed keys by using a Resource Manager template, update your template with the following changes:
148+
149+
1. In the **azuredeploy.json** file, add the following property to the resources" object:
150+
151+
```json
152+
"diskEncryptionProperties":
153+
{
154+
"vaultUri": "[parameters('diskEncryptionVaultUri')]",
155+
"keyName": "[parameters('diskEncryptionKeyName')]",
156+
"keyVersion": "[parameters('diskEncryptionKeyVersion')]",
157+
"msiResourceId": "[parameters('diskEncryptionMsiResourceId')]"
158+
}
159+
160+
1. In the **azuredeploy.parameters.json** file, add the following parameters. You can get the values of these parameters from the Key Vault URI and the managed Identity. For example, if you have the following URI and identity values,
161+
* Sample key vault URI: https://<KeyVault_Name>.vault.azure.net/keys/clusterkey/<Cluster_Key_Value>
162+
* Sample user-assigned managed identity: "/subscriptions/<subscriptionID>/resourcegroups/<ResourceGroup_Name>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<MSI_Name>
163+
164+
The parameters in the **azuredeploy.parameters.json** file are:
165+
166+
```json
167+
"diskEncryptionVaultUri": {
168+
"value": "https://<KeyVault_Name>.vault.azure.net"
169+
},
170+
"diskEncryptionKeyName": {
171+
"value": "clusterkey"
172+
},
173+
"diskEncryptionKeyVersion": {
174+
"value": "<Cluster_Key_Value>"
175+
},
176+
"diskEncryptionMsiResourceId": {
177+
"value": "/subscriptions/<subscriptionID>/resourcegroups/<ResourceGroup_Name>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<MSI_Name>"
178+
}
179+
```
180+
145181
## FAQ for customer-managed key encryption
146182

147183
**How does the HDInsight cluster access my key vault?**

0 commit comments

Comments
 (0)