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
Copy file name to clipboardExpand all lines: articles/stream-analytics/kafka-output.md
+10-13Lines changed: 10 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,12 @@ ms.topic: conceptual
8
8
ms.date: 09/26/2023
9
9
---
10
10
11
-
# Kafka Output from Azure Stream Analytics (Preview)
11
+
# Kafka output from Azure Stream Analytics (Preview)
12
12
13
13
Azure Stream Analytics allows you to connect directly to Kafka clusters as a producer to output data. The solution is low code and entirely managed by the Azure Stream Analytics team at Microsoft, allowing it to meet business compliance standards. The Kafka Adapters are backward compatible and support all versions with the latest client release starting from version 0.10. Users can connect to Kafka clusters inside a VNET and Kafka clusters with a public endpoint, depending on the configurations. The configuration relies on existing Kafka configuration conventions.
14
-
15
-
### Kafka Event Compression
16
-
17
14
Supported compression types are None, Gzip, Snappy, LZ4, and Zstd.
18
15
19
-
## Authentication and Encryption
16
+
## Authentication and encryption
20
17
21
18
You can use four types of security protocols to connect to your Kafka clusters:
22
19
@@ -30,25 +27,25 @@ You can use four types of security protocols to connect to your Kafka clusters:
30
27
31
28
32
29
> [!IMPORTANT]
33
-
> Confluent Cloud supports authenticating using API Keys, OAuth, or SAML single sign-on (SSO). Azure Stream Analytics does not currently support these authentication options. There will be an update shortly to support authenticating to the confluent cloud using API Keys.
30
+
> Confluent Cloud supports authenticating using API Keys, OAuth, or SAML single sign-on (SSO). Azure Stream Analytics does not currently support these authentication options.
34
31
>
35
32
36
33
37
-
### Key Vault Integration
34
+
### Key vault integration
38
35
39
36
> [!NOTE]
40
-
> When using trust store certificates with mTLS or SASL_SSL security protocols, you must have Azure KeyVault and managed identity configured for your Azure Stream Analytics job.
37
+
> When using trust store certificates with mTLS or SASL_SSL security protocols, you must have Azure Key vault and managed identity configured for your Azure Stream Analytics job.
41
38
>
42
-
Azure Stream Analytics integrates seamlessly with Azure Key Vault to access stored secrets needed for authentication and encryption when using mTLS or SASL_SSL security protocols. Your Azure Stream Analytics job connects to Azure Key Vault using managed identity to ensure a secure connection and avoid the exfiltration of secrets.
39
+
Azure Stream Analytics integrates seamlessly with Azure Key vault to access stored secrets needed for authentication and encryption when using mTLS or SASL_SSL security protocols. Your Azure Stream Analytics job connects to Azure Key vault using managed identity to ensure a secure connection and avoid the exfiltration of secrets.
43
40
44
-
You can store the certificates as Key Vault certificates or Key Vault secrets. Private keys are in PEM format.
41
+
You can store the certificates as Key Vault certificates or Key vault secrets. Private keys are in PEM format.
45
42
46
-
### Key Vault Integration
43
+
### VNET integration
47
44
When configuring your Azure Stream Analytics job to connect to your Kafka clusters, depending on your configuration, you may have to configure your job to access your Kafka clusters, which are behind a firewall or inside a virtual network. You can visit the Azure Stream Analytics VNET documentation to learn more about configuring private endpoints to access resources inside a virtual network or behind a firewall.
48
45
49
46
50
47
### Configuration
51
-
The following table lists the property names and their description for creating a Kafka Output:
48
+
The following table lists the property names and their description for creating a Kafka output:
0 commit comments