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

This topic presents the steps for configuring the MongoDB Atlas Sink connector in the Confluent Cloud private networking with the AWS PrivateLink and Egress Access Point.

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 running within an AWS PrivateLink 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.

To configure the MongoDB Atlas Sink connector with the AWS PrivateLink and Egress Access Points:

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

    1. Go to Network Access → Private Endpoint → Dedicated 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 name which will be required for creating a Confluent Cloud Egress Access Point.

      ../../_images/atlas-db-service-name.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.

  2. In Confluent Cloud, create an Egress Access Point.

    1. In the Network management tab, click the associated PrivateLink network.

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

    3. Specify:

      • Name: Specify a name for this access point.
      • Privatelink service name: Specify the MongoDB Atlas Service name from the first step above.
      ../../_images/ccloud-create-eap.png

    4. Click Save.

    5. Once the state of the Egress Access Point changes from Provisioning to Pending, make a note of the Endpoint ID. The value is required to finish setting up a private endpoint for MongoDB Atlas.

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

  3. In the MongoDB console, configure the MongoDB private endpoint.

    1. Click Edit for the previously created MongoDB private endpoint.

    2. Click Next.

    3. In Your VPC Endpoint ID field, specify the Endpoint ID associated with your Confluent Cloud Egress Access point, and click Save.

      You can enter the Endpoint ID in the MongoDB console as shown below:

      ../../_images/vpc-endpoint-id.png

    4. Once Endpoint Status changes to “Available”, you are ready to create the Confluent Cloud MongoDB Sink connector.

  4. Create MongoDB Atlas Sink connector.

    1. Go to your associated Dedicated cluster. In the Connectors tab, click MongoDB Atlas Sink.

    2. Select the source topic.

    3. Specify the Kafka authentication mechanism.

    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 Endpoint → Shell.

      3. Get the endpoint.

        ../../_images/atlas-db-endpoint.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.

        ../../_images/connection-host.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”.