Replicate MongoDB® Collections via AWS PrivateLink

SingleStore supports loading data from MongoDB® using CDC pipelines via AWS PrivateLink.

To replicate your MongoDB® databases using private links:

  1. Create an outbound connection from SingleStore. Refer to Connect to SingleStore Helios using AWS PrivateLink for more information.

    While configuring the outbound connection, on the Create Connection dialog, enter or select the following information:

    1. Endpoint: Select SingleStore Endpoint.

    2. Service Name: Enter your MongoDB® Atlas Endpoint Service Name.

    Even though data is ingested into SingleStore, an outbound connection is used because the ingestion process is initiated by connecting from SingleStore Helios to the AWS instance/resource.

  2. Request the VPC ID and Subnet ID for the AWS instance that hosts your SingleStore Helios workspace.

    Contact SingleStore Support and provide the following information:

    • Workspace ID and name.

    • In the support ticket, specify that the request is for VPC ID and Subnet ID for the AWS instance that hosts this workspace.

  3. Set up a private endpoint to the MongoDB® Atlas cluster using AWS PrivateLink. Specify the VPC ID and Subnet ID received from SingleStore while configuring the private endpoint in MongoDB®. Refer to Configure Private Endpoints for more information.

  4. Ensure that the Prerequisites are met.

  5. Copy the Service Name of your outbound connection from the Cloud Portal.

    1. Select <your_workspace_group> > Firewall > Private Links.

    2. Under the Actions column of your private connection, select the three dots, and select View Connection.

    3. From the View Connection dialog, copy the VPC Endpoint Service Name.

  6. Create a link to the VPC Endpoint Service. Specify the Service Name copied earlier in the mongodb.hosts parameter. For example:

    CREATE LINK <link_name> AS MONGODB
    CONFIG '{
    "mongodb.hosts": "<vpc_endpoint_service_name>"
    [, "mongodb.ssl.enabled":"true" ]
    [, "mongodb.authsource":"admin" ]}'
    CREDENTIALS
    '{"mongodb.password": "<password>", "mongodb.user": "<user>"}';

    Refer to CREATE LINK for more information.

  7. Replicate the tables.

    CREATE TABLES AS INFER PIPELINE AS LOAD DATA
    LINK <link_name> "*" FORMAT AVRO;
    START ALL PIPELINES;

    Refer to Replicate MongoDB® Collections using SQL for more information.

Last modified: August 9, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK