Skip to content

Commit e5852e2

Browse files
authored
Merge pull request #102537 from dagiro/byok1
byok1
2 parents 1782634 + 031ac82 commit e5852e2

8 files changed

+6
-6
lines changed

articles/hdinsight/kafka/apache-kafka-byok.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: hrasheed
66
ms.reviewer: hrasheed
77
ms.service: hdinsight
88
ms.topic: conceptual
9-
ms.date: 12/09/2019
9+
ms.date: 01/27/2020
1010
---
1111

1212
# Bring your own key for Apache Kafka on Azure HDInsight
@@ -34,13 +34,13 @@ To create a BYOK enabled Kafka cluster, we'll go through the following steps:
3434

3535
To authenticate to Key Vault, create a user-assigned managed identity using the [Azure portal](../../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md), [Azure PowerShell](../../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-powershell.md), [Azure Resource Manager](../../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-arm.md), or [Azure CLI](../../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-cli.md). For more information on how managed identities work in Azure HDInsight, see [Managed identities in Azure HDInsight](../hdinsight-managed-identities.md). While Azure Active directory is required for managed identities and BYOK to Kafka, Enterprise Security Package (ESP) isn't a requirement. Be sure to save the managed identity resource ID for when you add it to the Key Vault access policy.
3636

37-
![Create user-assigned managed identity in Azure portal](./media/apache-kafka-byok/user-managed-identity-portal.png)
37+
![Create user-assigned managed identity in Azure portal](./media/apache-kafka-byok/azure-portal-create-managed-identity.png)
3838

3939
## Set up the Key Vault and keys
4040

4141
HDInsight only supports Azure Key Vault. If you have your own key vault, you can import your keys into Azure Key Vault. Remember that the keys must have "Soft Delete". The "Soft Delete" feature is available through the REST, .NET/C#, PowerShell, and Azure CLI interfaces.
4242

43-
1. To create a new key vault, follow the [Azure Key Vault](../../key-vault/key-vault-overview.md) quickstart. For more information about importing existing keys, visit [About keys, secrets, and certificates](../../key-vault/about-keys-secrets-and-certificates.md).
43+
1. To create a new key vault, follow the [Azure Key Vault](../../key-vault/quick-create-cli.md) quickstart. For more information about importing existing keys, visit [About keys, secrets, and certificates](../../key-vault/about-keys-secrets-and-certificates.md).
4444

4545
1. Enable "soft-delete" on the key-vault by using the [az keyvault update](/cli/azure/keyvault?view=azure-cli-latest#az-keyvault-update) CLI command.
4646

@@ -74,7 +74,7 @@ HDInsight only supports Azure Key Vault. If you have your own key vault, you can
7474
7575
b. Under **Select Principal**, choose the user-assigned managed identity you created.
7676
77-
![Set Select Principal for Azure Key Vault access policy](./media/apache-kafka-byok/add-key-vault-access-policy-select-principal.png)
77+
![Set Select Principal for Azure Key Vault access policy](./media/apache-kafka-byok/azure-portal-add-access-policy.png)
7878
7979
c. Set **Key Permissions** to **Get**, **Unwrap Key**, and **Wrap Key**.
8080
@@ -92,9 +92,9 @@ HDInsight only supports Azure Key Vault. If you have your own key vault, you can
9292
9393
You're now ready to create a new HDInsight cluster. BYOK can only be applied to new clusters during cluster creation. Encryption can't be removed from BYOK clusters, and BYOK can't be added to existing clusters.
9494
95-
![Kafka disk encryption in Azure portal](./media/apache-kafka-byok/azure-portal-cluster-security-networking-kafka-byok.png)
95+
![Kafka disk encryption in Azure portal](./media/apache-kafka-byok/azure-portal-cluster-security-networking-kafka.png)
9696
97-
During cluster creation, provide the full key URL, including the key version. For example, `https://contoso-kv.vault.azure.net/keys/kafkaClusterKey/46ab702136bc4b229f8b10e8c2997fa4`. You also need to assign the managed identity to the cluster and provide the key URI.
97+
During cluster creation, provide the full key URL, including the key version. For example, `https://contoso-kv.vault.azure.net/keys/kafkaClusterKey/46ab702136bc4b229f8b10e8c2997fa4`. You also need to assign the managed identity to the cluster and provide the key URI. For complete cluster creation details, see [Create Apache Hadoop clusters using the Azure portal](./apache-kafka-get-started.md)
9898
9999
## Rotating the Encryption key
100100
73.6 KB
Loading
86.7 KB
Loading
259 KB
Loading
144 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)