Skip to content

Commit 5388b0d

Browse files
authored
Improved Acrolinx Score
Improved Acrolinx Score
1 parent 42cf824 commit 5388b0d

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/hdinsight/kafka/apache-esp-kafka-ssl-encryption-authentication.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ This article shows you how to set up Transport Layer Security (TLS) encryption,
1616
1717
## Apache Kafka broker setup
1818

19-
The Kafka TLS broker setup will use four HDInsight cluster VMs in the following way:
19+
The Kafka TLS broker setup uses four HDInsight cluster VMs in the following way:
2020

2121
* headnode 0 - Certificate Authority (CA)
2222
* worker node 0, 1, and 2 - brokers
2323

2424
> [!Note]
25-
> This guide will use self-signed certificates, but the most secure solution is to use certificates issued by trusted CAs.
25+
> This guide uses self-signed certificates, but the most secure solution is to use certificates issued by trusted CAs.
2626
2727
The summary of the broker setup process is as follows:
2828

@@ -42,7 +42,7 @@ Use the following detailed instructions to complete the broker setup:
4242
> [!Important]
4343
> In the following code snippets wnX is an abbreviation for one of the three worker nodes and should be substituted with `wn0`, `wn1` or `wn2` as appropriate. `WorkerNode0_Name` and `HeadNode0_Name` should be substituted with the names of the respective machines.
4444
45-
1. Perform initial setup on head node 0, which for HDInsight will fill the role of the Certificate Authority (CA).
45+
1. Perform initial setup on head node 0, which for HDInsight fills the role of the Certificate Authority (CA).
4646

4747
```bash
4848
# Create a new directory 'ssl' and change into it
@@ -76,7 +76,7 @@ Use the following detailed instructions to complete the broker setup:
7676
wn0-espkaf.securehadooprc.onmicrosoft.com
7777
wn0-kafka2.zbxwnwsmpcsuvbjqbmespcm1zg.bx.internal.cloudapp.net
7878
```
79-
:::image type="content" source="./media/apache-esp-kafka-ssl-encryption-authentication/etc-hosts.png" alt-text="Screenshot showing etc hosts file output." border="true":::
79+
:::image type="content" source="./media/apache-esp-kafka-ssl-encryption-authentication/etc-hosts.png" alt-text="Screenshot showing host file output." border="true":::
8080

8181
1. On the CA machine, run the following command to create ca-cert and ca-key files:
8282

@@ -134,7 +134,7 @@ To complete the configuration modification, do the following steps:
134134
135135
136136
> [!Note]
137-
> This step is only required if you are setting up authentication and encryption.
137+
> This step is only required if you're setting up authentication and encryption.
138138

139139
:::image type="content" source="./media/apache-esp-kafka-ssl-encryption-authentication/editing-configuration-ambari2.png" alt-text="Screenshot showing how to edit Kafka ssl configuration properties in Ambari." border="true":::
140140

@@ -147,11 +147,11 @@ To complete the configuration modification, do the following steps:
147147
148148
For HDI version 4.0 or 5.0
149149
150-
a. If you are setting up authentication and encryption, then the screenshot will look like
150+
a. If you're setting up authentication and encryption, then the screenshot looks like
151151

152152
:::image type="content" source="./media/apache-esp-kafka-ssl-encryption-authentication/properties-file-authentication-as-required.png" alt-text="Screenshot showing how to edit Kafka-env template property in Ambari authentication as required." border="true":::
153153

154-
b. If you are setting up encryption only, then the screenshot will look like
154+
b. If you are setting up encryption only, then the screenshot looks like
155155

156156
:::image type="content" source="./media/apache-esp-kafka-ssl-encryption-authentication/properties-file-authentication-as-none.png" alt-text="Screenshot showing how to edit Kafka-env template property in Ambari authentication as none." border="true":::
157157

@@ -282,7 +282,7 @@ The details of each step are given.
282282
cd ssl
283283
```
284284
285-
1. Create client store with signed cert, and import ca cert into the keystore and truststore on client machine (hn1):
285+
1. Create client store with signed cert, and import CA certificate into the keystore and truststore on client machine (hn1):
286286
287287
```bash
288288
keytool -keystore kafka.client.truststore.jks -alias CARoot -import -file ca-cert -storepass "MyClientPassword123" -keypass "MyClientPassword123" -noprompt
@@ -292,7 +292,7 @@ The details of each step are given.
292292
keytool -keystore kafka.client.keystore.jks -import -file client-signed-cert -storepass "MyClientPassword123" -keypass "MyClientPassword123" -noprompt
293293
```
294294
295-
1. Create a file `client-ssl-auth.properties` on client machine (hn1) . It should have the following lines:
295+
1. Create a file `client-ssl-auth.properties` on client machine (hn1). It should have the following lines:
296296
297297
```bash
298298
security.protocol=SASL_SSL

0 commit comments

Comments
 (0)