Load Data from Estuary Flow

Integrate your SingleStore databases with Estuary Flow to build and manage real-time ETL and ELT data pipelines that capture and replicate database events to downstream applications.

You can configure SingleStore as a destination in Estuary Flow. Ingest data from Estuary Flow into SingleStore using Materializations.

Configure the SingleStore Destination

Use the SingleStore variant of the Kafka-compatible Dekaf connector to configure SingleStore as a destination in Estuary Flow.

Prerequisites

  • An Estuary Flow collection

  • An active SingleStore deployment

Connect to SingleStore from Estuary Flow

To configure SingleStore as a destination:

  1. Log in to Estuary Flow.

  2. Create a new materialization.

    1. On the Dashboard, select Destinations from the left navigation pane.

    2. On the Destinations page, select NEW MATERIALIZATION.

    3. On the Create Materialization page, from the list of connectors, search and select the SingleStore connector.

    4. Enter or select the following information:

      1. Name: Enter a name for the materialization.

      2. Data Plane: Select a data plane to use.

      3. Auth Token: Specify an authentication token. This token is used to authenticate Kafka consumers to this materialization task.

    5. Link a capture (collection) to this task.

    6. Select NEXT > TEST to test the materialization.

    7. Select SAVE AND PUBLISH to publish this task.

  3. Log in to your SingleStore deployment.

  4. Create a table to store the ingested data. For example:

    CREATE TABLE estuaryFlow
    (id INT, created DATETIME(6), product_ids JSON);
  5. Create a pipeline to ingest the data from Estuary Flow. For example:

    CREATE PIPELINE estuaryIngest AS
    LOAD DATA KAFKA "dekaf.estuary-data.com:9092/<collection_name>"
    CONFIG '{
    "security.protocol":"SASL_SSL",
    "sasl.mechanism":"PLAIN",
    "sasl.username":"{<materialization_name>}",
    "broker.address.family": "v4",
    "schema.registry.username": "{<materialization_name>}",
    "fetch.wait.max.ms": "2000"
    }'
    CREDENTIALS '{
    "sasl.password": "<auth_token>",
    "schema.registry.password": "<auth_token>"
    }'
    INTO TABLE estuaryFlow
    FORMAT AVRO SCHEMA REGISTRY 'https://dekaf.estuary-data.com'
    ( id <- id, created <- created, product_ids <- product_ids );

    where,

    • collection_name: Name of the collection linked to the materialization task.

    • materialization_name: Name of the Estuary Flow materialization.

    • auth_token: Authentication token specified for the materialization.

  6. Start the pipeline. For example:

    START PIPELINE estuaryIngest;

The pipeline starts ingesting data from the Estuary Flow collection to the SingleStore table. Run the SHOW PIPELINES command to view the status of the pipeline.

Refer to SingleStore | Estuary Flow for more information, for example, configuration properties.

Last modified: October 10, 2025

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