Skip to content

Commit 7a61fc3

Browse files
committed
edit pass: six-azure-managed-instance-for-apache-cassandra-articles
1 parent a74009f commit 7a61fc3

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/managed-instance-apache-cassandra/customer-managed-keys.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions, devx-track-azurecli
1212

1313
# Customer-managed keys in Azure Managed Instance for Apache Cassandra
1414

15-
In Azure Managed Instance for Apache Cassandra, you can encrypt data on disk by using your own key. This article describes how to implement customer-managed keys by using Azure Key Vault.
15+
In Azure Managed Instance for Apache Cassandra, you can use your own key to encrypt data on disk. This article describes how to implement customer-managed keys by using Azure Key Vault.
1616

1717
## Prerequisites
1818

@@ -71,7 +71,7 @@ This article requires Azure CLI version 2.30.0 or later. If you're using Azure C
7171
7272
:::image type="content" source="./media/cmk/key-vault-access-policy-1.png" alt-text="Screenshot that shows the pane for access policies in the Azure portal." lightbox="./media/cmk/key-vault-access-policy-1.png" border="true":::
7373
74-
1. For **Key permissions**, select **get**, **wrap**, and **unwrap**. Choose the **Select principal** box to open the **Principal** pane. Enter the cluster's `principalId` value that you retrieved earlier, and then choose the **Select** button. (In the portal, you can also look up the principal ID of the cluster by the cluster's name.)
74+
1. For **Key permissions**, select **get**, **wrap**, and **unwrap**. Select the **Select principal** box to open the **Principal** pane. Enter the cluster's `principalId` value that you retrieved earlier, and then select the **Select** button. (In the portal, you can also look up the principal ID of the cluster by the cluster's name.)
7575
7676
:::image type="content" source="./media/cmk/key-vault-access-policy-2.png" alt-text="Screenshot that shows an example of adding a principal for an access policy." lightbox="./media/cmk/key-vault-access-policy-2.png" border="true":::
7777
@@ -82,19 +82,19 @@ This article requires Azure CLI version 2.30.0 or later. If you're using Azure C
8282
8383
:::image type="content" source="./media/cmk/save.png" alt-text="Screenshot that shows the button for saving an access policy." lightbox="./media/cmk/key-vault-access-policy-2.png" border="true":::
8484
85-
1. To get the key identifier, select your key.
85+
1. To get the key identifier, select **Keys**, and then select your key.
8686
87-
:::image type="content" source="./media/cmk/select-key.png" alt-text="Select key" lightbox="./media/cmk/key-identifier-1.png" border="true":::
87+
:::image type="content" source="./media/cmk/select-key.png" alt-text="Screenshot that shows the pane for selecting a key." lightbox="./media/cmk/key-identifier-1.png" border="true":::
8888
89-
1. Select the current version:
89+
1. Select the current version.
9090
91-
:::image type="content" source="./media/cmk/current-version.png" alt-text="Select current version" lightbox="./media/cmk/key-identifier-1.png" border="true":::
91+
:::image type="content" source="./media/cmk/current-version.png" alt-text="Screenshot that shows the box for selecting the current version of a key." lightbox="./media/cmk/key-identifier-1.png" border="true":::
9292
9393
1. Save the key identifier for later use.
9494
95-
:::image type="content" source="./media/cmk/key-identifier-2.png" alt-text="Key identifier step 2" lightbox="./media/cmk/key-identifier-1.png" border="true":::
95+
:::image type="content" source="./media/cmk/key-identifier-2.png" alt-text="Screenshot that shows copying a key identifier to the clipboard." lightbox="./media/cmk/key-identifier-1.png" border="true":::
9696
97-
1. Create the datacenter by replacing `<key identifier>` with the same key (the uri you copied in previous step) for both managed disk (managed-disk-customer-key-uri) and backup storage (backup-storage-customer-key-uri) encryption as shown below (use the same value for `subnet` you used earlier):
97+
1. Create the datacenter by replacing `<key identifier>` with the same key (the URI that you copied in the previous step) for both managed disk (`managed-disk-customer-key-uri`) and backup storage (`backup-storage-customer-key-uri`) encryption. Use the same value for `subnet` that you used earlier.
9898
9999
```azurecli-interactive
100100
managedDiskKeyUri = "<key identifier>"
@@ -118,11 +118,11 @@ This article requires Azure CLI version 2.30.0 or later. If you're using Azure C
118118
--sku Standard_DS14_v2
119119
```
120120
121-
1. An existing cluster with no identity information can be assigned an identity as shown below:
121+
You can also assign an identity to an existing cluster with no identity information:
122122
123-
```azurecli-interactive
124-
az managed-cassandra cluster update --identity-type SystemAssigned -g $group -c $cluster
125-
```
123+
```azurecli-interactive
124+
az managed-cassandra cluster update --identity-type SystemAssigned -g $group -c $cluster
125+
```
126126

127127
## <a id="update-cluster"></a>Rotate the key
128128

0 commit comments

Comments
 (0)