Connect to MongoDB® using Azure Private Link

SingleStore supports connecting to a MongoDB® instance via Azure Private Link.

Prerequisites

Configure the Connection

To connect to the MongoDB® instance using Azure Private Link:

  1. Copy the VPC Endpoint Service Name from the SingleStore Helios Cloud Portal.

    1. On the Cloud Portal, select Workspaces in the left navigation pane.

    2. Select the three dots under the Actions column for your workspace, and select Access & Security from the list.

    3. On the Access tab, under Private Links, select Create Connection.

    4. On the Create Connection dialog, copy and store the Private Link Service Alias. The Endpoint and Connection Type fields are automatically set to MongoDB® and Inbound, respectively.

    5. (Optional) Keep the Create Connection dialog open to enter the resource ID of your Azure private endpoint created in the next step.

  2. Create a private endpoint on the Azure portal. While configuring the connection, perform the following tasks:

    1. Under Resource, select Connect to an Azure resource by resource ID or alias. Enter the Private Link Service alias copied in the previous step in the Resource ID or alias field.

    2. Allow incoming connections to TCP port 27017 of your private endpoint.

    3. Approve the private endpoint connection request.

    4. Copy the Private Endpoint Resource ID of your Azure private endpoint. The resource ID has the following format:

      /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Network/privateEndpoints/<endpoint-name>

  3. Create an inbound private connection on the Cloud Portal. On the Create Connection dialog from the first step, enter the Private Endpoint Resource ID. The Endpoint and Connection Type fields are automatically set to MongoDB® and Inbound, respectively.

  4. Select Create Connection.

The connection is ready to use once it is in ACTIVE state. Connect to the MongoDB® endpoint using the following connection string (update the credentials and private endpoint address):

mongodb://<username>:<password>@<private-endpoint-address>:27017/?authMechanism=PLAIN&tls=true&loadBalanced=true&tlsAllowInvalidHostnames=true&tlsAllowInvalidCertificates=true

Refer to Connect to SingleStore Helios Workspaces from Private Networks/Services via Azure Private Link for related information.

Last modified:

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.