MongoDB Atlas Sink Connector for Confluent Cloud with Azure Egress Access Point

This topic presents the steps for configuring the MongoDB Atlas Sink connector in Confluent Cloud with Azure Private Link and Egress Access Point.

Prerequisites

The following is a list of prerequisites for configuring the MongoDB Altas connector with an Egress Access Point:

  • A Confluent Cloud Dedicated cluster was set up and is running within an Azure Private Link network.
  • A Dedicated MongoDB Atlas database was created to sink data into and is running within the same region and cloud as the Confluent Cloud cluster.
  • A source topic was created to sink data into MongoDB Atlas.

Step 1. Create a MongoDB Private Endpoint

In MongoDB, create a Private Endpoint for for your Dedicated MongoDB Atlas database:

  1. Go to Network AccessPrivate EndpointDedicated Cluster.

  2. Click Add Private Endpoint.

  3. Select the applicable cloud provider and region of your Dedicated MongoDB Atlas database.

  4. Make a note of the Atlas Endpoint Service value which is required for creating a Confluent Cloud Egress Access Point.

    ../../_images/atlas-endpoint-service1.png
  5. You can close the workflow for now. You will edit the rest of the configuration after you create a VPC endpoint ID in Confluent Cloud.

Step 2. Create an Egress Access Point

  1. In the Confluent Cloud Console, in the Network management tab, click the associated Private Link network.

  2. In the Egress access points tab, click Create access point.

  3. Specify the following:

    • Name: Specify a name for this access point.
    • Azure Resource ID: Specify the MongoDB Atlas Service value from the first step above.
    • Sub-resource name: Leave it blank as it is only applicable for the 1st party Azure services.
    ../../_images/ccloud-create-eap1.png
  4. Click Save.

  5. Once the status of the Egress Access Point changes from “Provisioning” to “Pending”, make a note of the Resource ID and IP Address values. The values are required to finish setting up a private endpoint for MongoDB Atlas.

    ../../_images/atlas-db-resource-id.png

Step 3. Configure the MongoDB private endpoint

  1. In the MongoDB console, click Edit for the previously created MongoDB private endpoint.

  2. Click Next.

  3. Specify the Endpoint Resource ID and Private Endpoint IP Address associated with your Confluent Cloud Egress Access point. Click Create.

    ../../_images/private-endpoint-resource-id.png
  4. Once Endpoint Status changes to “Available”, you are ready to create the Confluent Cloud MongoDB Sink connector.

Step 4. Create the MongoDB Atlas Sink connector

  1. In the Confluent Cloud Console, go to your associated Dedicated cluster. In Connectors, click MongoDB Atlas Sink.

  2. Select the source topic, and click Continue.

  3. Specify the Kafka authentication mechanism, and click Continue.

  4. Specify the authentication details for MongoDB.

    1. In the MongoDB Atlas console, click Database under Deployment.

    2. Click Connect for the associated database → Private EndpointShell.

    3. Get the endpoint as shown.

      ../../_images/atlas-db-endpoint1.png
    4. In Confluent Cloud, specify the MongoDB credentials during the connector creation steps.

      In the Connection host field, specify the endpoint you retrieved in the previous step.

      Note

      When you configure a private endpoint, ensure that the standard hostname has “-pl-0” appended to its first part, as shown in the screen below.

      ../../_images/connection-host1.png
  5. Specify configuration details for the connector.

  6. Specify sizing (number of tasks) for the connector.

  7. Review and launch the connector.

When the connector is successfully launched, the connector status becomes “Running”.