Skip to content

Commit b7871d3

Browse files
PMEds28PMEds28
authored
Merge pull request #269086 from maud-lv/ml-scconfluent
Add Service Connector instructions
2 parents be9a00e + 82465f1 commit b7871d3

File tree

7 files changed

+102
-10
lines changed

7 files changed

+102
-10
lines changed

‎articles/partner-solutions/apache-kafka-confluent-cloud/add-connectors.md

Lines changed: 102 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,117 @@
11
---
2-
title: Azure services and Confluent Cloud integration
3-
description: This article describes how to use Azure services and install connectors for Confluent Cloud integration.
4-
# customerIntent: As a developer I want set up connectors between Confluent Cloud and Azure services.
5-
ms.topic: conceptual
6-
ms.date: 1/31/2024
7-
2+
title: Connect a Confluent organization to other Azure resources
3+
description: Learn how to connect an instance of Apache Kafka® & Apache Flink® on Confluent Cloud™ to other Azure services using Service Connector.
4+
# customerIntent: As a developer I want connect Confluent Cloud to Azure services.
5+
ms.topic: how-to
6+
ms.date: 04/09/2024
7+
ms.custom: ai-gen-docs-bap, ai-gen-desc, ai-seo-date:04/09/2024
88
---
99

10-
# Azure services and Confluent Cloud integrations
10+
# Connect a Confluent organization to other Azure resources
11+
12+
In this guide, learn how to connect an instance of Apache Kafka® & Apache Flink® on Confluent Cloud™ - An Azure Native ISV Service, to other Azure services, using Service Connector. This page also introduces Azure Cosmos DB connectors and the Azure Functions Kafka trigger extension.
13+
14+
Service Connector is an Azure service designed to simplify the process of connecting Azure resources together. Service Connector manages your connection's network and authentication settings to simplify the operation.
15+
16+
This guide shows step by step instructions to connect an app deployed to Azure App Service to a Confluent organization. You can apply a similar method to connect your Confluent organization to other services supported by Service Connector.
17+
18+
## Prerequisites
19+
20+
* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free)
21+
* An existing Confluent organization. If you don't have one yet, refer to [create a Confluent organization](./create-cli.md)
22+
* An app deployed to [Azure App Service](/azure/app-service/quickstart-dotnetcore), [Azure Container Apps](/azure/container-apps/quickstart-portal), [Azure Spring Apps](/azure/spring-apps/enterprise/quickstart), or [Azure Kubernetes Services (AKS)](/azure/aks/learn/quick-kubernetes-deploy-portal).
23+
24+
## Create a new connection
25+
26+
Follow these steps to connect an app to Apache Kafka & Apache Flink on Confluent Cloud.
27+
28+
1. Open your App Service, Container Apps, or Azure Spring Apps, or AKS resource. If using Azure Spring Apps, you must then open the **Apps** menu and select your app.
29+
30+
1. Open **Service Connector** from the left menu and select **Create**.
31+
32+
:::image type="content" source="./media/connect/create-connection.png" alt-text="Screenshot from the Azure portal showing the Create button.":::
33+
34+
1. Enter or select the following information.
35+
36+
| Setting | Example | Description |
37+
|---------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
38+
| **Service type** | *Apache Kafka on Confluent Cloud* | Select **Apache Kafka on Confluent Cloud** to generate a connection to a Confluent. organization. |
39+
| **Connection name** | *Confluent_d0fcp* | The connection name that identifies the connection between your App Service and Confluent organization service. Use the connection name provided by Service Connector or enter your own connection name. Connection names can only contain letters, numbers (0-9), periods ("."), and underscores ("_"). |
40+
| **Source** | *Azure marketplace Confluent resource (preview)* | Select **Azure marketplace Confluent resource (preview)**. |
41+
42+
:::image type="content" source="./media/connect/confluent-source.png" alt-text="Screenshot from the Azure portal showing the Source options.":::
43+
44+
1. Refer to the two tabs below for instructions to connect to a Confluent resource deployed via Azure Marketplace or deployed directly on the Confluent user interface.
45+
46+
> [!IMPORTANT]
47+
> Service Connector for Azure Marketplace Confluent resources is currently in PREVIEW.
48+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
49+
50+
### [Azure marketplace Confluent resource](#tab/marketplace-confluent)
51+
52+
If your Confluent resource is deployed through Azure Marketplace, enter or select the following information.
53+
54+
| Setting | Example | Description |
55+
|---------------------------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------|
56+
| **Subscription** | *my subscription* | Select the subscription that holds your Confluent organization. |
57+
| **Confluent Service** | *my-confluent-org* | Select the subscription that holds your Confluent organization. |
58+
| **Environment** | *demoenv1* | Select your Confluent organization environment. |
59+
| **Cluster** | *ProdKafkaCluster* | Select your Confluent organization cluster. |
60+
| **Create connection for Schema Registry** | Unchecked | This option is unchecked by default. Optionally check the box to create a connection for the schema registry. |
61+
| **Client type** | *Node.js* | Select the app stack that's on your compute service instance. |
62+
63+
:::image type="content" source="./media/connect/marketplace-basic.png" alt-text="Screenshot from the Azure portal showing Service Connector basic creation fields for an Azure Marketplace Confluent resource.":::
64+
65+
### [Azure non-marketplace Confluent resource](#tab/non-marketplace-confluent)
66+
67+
If your Confluent resource is deployed directly through Azure services, rather than through Azure Marketplace, select or enter the following information.
68+
69+
| Setting | Example | Description |
70+
|-------------------------------------------|------------------------------------------|-----------------------------------------------------------------------------------------|
71+
| **Kafka bootstrap server URL** | *xxxx.eastus.azure.confluent.cloud:9092* | Enter your Kafka bootstrap server URL. |
72+
| **Create connection for Schema Registry** | Unchecked | This option is unchecked by default. Optionally check the box to use a schema registry. |
73+
| **Client type** | *Node.js* | Select the app stack that's on your compute service instance. |
74+
75+
:::image type="content" source="./media/connect/non-marketplace-basic.png" alt-text="Screenshot from the Azure portal showing Service Connector basic creation fields for an Azure Marketplace Confluent resource.":::
76+
77+
---
78+
79+
1. Select **Next: Authentication**.
80+
81+
* The **Connection string** authentication type is selected by default.
82+
* For **API Keys**, choose **Create New**. If you already have an API key, alternatively select **Select Existing**, then enter the Kafka API key and secret. If you're using an existing API key and selected the option to enable schema registry in the previous tab, enter the schema registry URL, schema registry API key and schema registry API secret.
83+
* An **Advanced** option also lets you edit the configuration variable names.
84+
85+
:::image type="content" source="./media/connect/authentication.png" alt-text="Screenshot from the Azure portal showing connection authentication settings.":::
86+
87+
1. Select **Next: Networking** to configure the network access to your Confluent organization. **Configure firewall rules to enable access to your target service** is selected by default. Optionally also configure the webapp's outbound traffic to intergate with Virtual Network.
88+
89+
:::image type="content" source="./media/connect/networking.png" alt-text="Screenshot from the Azure portal showing connection networking settings.":::
90+
91+
1. Select **Next: Review + Create** to review the provided information and select **Create**.
92+
93+
## View and edit connections
94+
95+
To review your existing connections, in the Azure portal, go to your application deployed to Azure App Service, Azure Container Apps, Azure Spring Apps, or AKS and open Service Connector from the left menu.
96+
97+
Select a connection's checkbox and explore the following options:
98+
99+
* Select **>** to access connection details.
100+
* Select **Validate** to prompt Service Connector to check your connection.
101+
* Select **Edit** to edit connection details.
102+
* Select **Delete** to remove a connection.
11103

12-
This article describes how to use Azure services like Azure Functions, and how to install connectors to Azure resources for Apache Kafka® & Apache Flink® on Confluent Cloud™ - An Azure Native ISV Service.
104+
## Other solutions
13105

14-
## Azure Cosmos DB connector
106+
### Azure Cosmos DB connectors
15107

16108
**Azure Cosmos DB Sink Connector fully managed connector** is generally available within Confluent Cloud. The fully managed connector eliminates the need for the development and management of custom integrations, and reduces the overall operational burden of connecting your data between Confluent Cloud and Azure Cosmos DB. The Azure Cosmos DB Sink Connector for Confluent Cloud reads from and writes data to an Azure Cosmos DB database. The connector polls data from Kafka and writes to database containers.
17109

18110
To set up your connector, see [Azure Cosmos DB Sink Connector for Confluent Cloud](https://docs.confluent.io/cloud/current/connectors/cc-azure-cosmos-sink.html).
19111

20112
**Azure Cosmos DB Self Managed connector** must be installed manually. First download an uber JAR from the [Azure Cosmos DB Releases page](https://github.com/microsoft/kafka-connect-cosmosdb/releases). Or, you can [build your own uber JAR directly from the source code](https://github.com/microsoft/kafka-connect-cosmosdb/blob/dev/doc/README_Sink.md#install-sink-connector). Complete the installation by following the guidance described in the Confluent documentation for [installing connectors manually](https://docs.confluent.io/home/connect/install.html#install-connector-manually).
21113

22-
## Azure Functions
114+
### Azure Functions Kafka trigger extension
23115

24116
**Azure Functions Kafka trigger extension** is used to run your function code in response to messages in Kafka topics. You can also use a Kafka output binding to write from your function to a topic. For information about setup and configuration details, see [Apache Kafka bindings for Azure Functions overview](../../azure-functions/functions-bindings-kafka.md).
25117

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/authentication.png

77.3 KB
Loading

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/confluent-source.png

58.3 KB
Loading

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/create-connection.png

82.3 KB
Loading

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/marketplace-basic.png

40.2 KB
Loading

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/networking.png

99.1 KB
Loading

‎articles/partner-solutions/apache-kafka-confluent-cloud/media/connect/non-marketplace-basic.png

22.6 KB
Loading

0 commit comments

Comments
 (0)