You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following example shows how to use an Azure Resource Manager template to create a new Apache Spark cluster with disk encryption enabled. For more information, see [What are ARM templates?](https://docs.microsoft.com/azure/azure-resource-manager/templates/overview).
125
+
126
+
This example uses PowerShell to call the template.
"description": "The name of the HDInsight cluster to create."
162
+
}
163
+
},
164
+
"clusterLoginUserName": {
165
+
"type": "string",
166
+
"defaultValue": "admin",
167
+
"metadata": {
168
+
"description": "These credentials can be used to submit jobs to the cluster and to log into cluster dashboards."
169
+
}
170
+
},
171
+
"clusterLoginPassword": {
172
+
"type": "securestring",
173
+
"metadata": {
174
+
"description": "The password must be at least 10 characters in length and must contain at least one digit, one non-alphanumeric character, and one upper or lower case letter."
175
+
}
176
+
},
177
+
"location": {
178
+
"type": "string",
179
+
"defaultValue": "[resourceGroup().location]",
180
+
"metadata": {
181
+
"description": "The location where all azure resources will be deployed."
182
+
}
183
+
},
184
+
"sshUserName": {
185
+
"type": "string",
186
+
"defaultValue": "sshuser",
187
+
"metadata": {
188
+
"description": "These credentials can be used to remotely access the cluster."
189
+
}
190
+
},
191
+
"sshPassword": {
192
+
"type": "securestring",
193
+
"metadata": {
194
+
"description": "The password must be at least 10 characters in length and must contain at least one digit, one non-alphanumeric character, and one upper or lower case letter."
195
+
}
196
+
},
197
+
"headNodeSize": {
198
+
"type": "string",
199
+
"defaultValue": "Standard_D12_v2",
200
+
"metadata": {
201
+
"description": "The VM size of the head nodes."
202
+
}
203
+
},
204
+
"workerNodeSize": {
205
+
"type": "string",
206
+
"defaultValue": "Standard_D13_v2",
207
+
"metadata": {
208
+
"description": "The VM size of the worker nodes."
209
+
}
210
+
},
211
+
"diskEncryptionVaultUri": {
212
+
"type": "string",
213
+
"metadata": {
214
+
"description": "The Key Vault DNSname."
215
+
}
216
+
},
217
+
"diskEncryptionKeyName": {
218
+
"type": "string",
219
+
"metadata": {
220
+
"description": "The Key Vault key name."
221
+
}
222
+
},
223
+
"diskEncryptionKeyVersion": {
224
+
"type": "string",
225
+
"metadata": {
226
+
"description": "The Key Vault key version for the selected key."
227
+
}
228
+
},
229
+
"managedIdentityName": {
230
+
"type": "string",
231
+
"metadata": {
232
+
"description": "The user-assigned managed identity."
There might be scenarios where you might want to change the encryption keys used by the HDInsight cluster after it has been created. This can be easily via the portal. For this operation, the cluster must have access to both the current key and the intended new key, otherwise the rotate key operation will fail.
@@ -142,42 +356,6 @@ az hdinsight rotate-disk-encryption-key \
142
356
--resource-group MyResourceGroup
143
357
```
144
358
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:
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,
0 commit comments