Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Streams
    • All tutorials
    • Entering data into storage systems
    • Smart log processing
    • Transferring data within microservice architectures
    • Saving data to ClickHouse®
    • Replicating logs to Object Storage using Fluent Bit
    • Replicating logs to Object Storage using Data Streams
    • Migrating data to Yandex Object Storage using Yandex Data Transfer
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data from an Data Streams queue to Managed Service for YDB
    • Delivering data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • YDB change data capture and delivery to YDS
    • PostgreSQL change data capture and delivery to YDS
    • MySQL® change data capture and delivery to YDS
    • Streaming Yandex Cloud Postbox events to Yandex Data Streams and analyzing them using Yandex DataLens
    • Creating an interactive serverless application using WebSocket
    • Processing Audit Trails events
    • Processing CDC Debezium streams
    • Exporting audit logs to MaxPatrol SIEM
    • Searching for Yandex Cloud events in Yandex Query
  • Access management
  • Pricing policy
  • FAQ

In this article:

  • Required paid resources
  • Getting started
  • Set up a Data Streams-enabled stream
  • Set up and activate the transfer
  • Test your transfer
  • Delete the resources you created
  1. Tutorials
  2. Saving data to ClickHouse®

Saving data to Yandex Managed Service for ClickHouse®

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Getting started
  • Set up a Data Streams-enabled stream
  • Set up and activate the transfer
  • Test your transfer
  • Delete the resources you created

With Data Transfer, you can deliver data from a data stream Data Streams to Managed Service for ClickHouse®.

To transfer data:

  1. Set up a stream in Data Streams.
  2. Set up and activate your transfer.
  3. Test your transfer.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

  • Managed Service for ClickHouse® cluster fee: Using computing resources allocated to hosts (including ZooKeeper hosts) and disk space (see Managed Service for ClickHouse® pricing).

  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

  • Fee for the Managed Service for YDB database. The charge depends on the usage mode:

    • For the serverless mode, you pay for data operations and the amount of stored data.
    • For the dedicated instance mode, you pay for the use of computing resources, dedicated DBs, and disk space.

    Learn more about the Managed Service for YDB pricing plans.

  • Data Streams fee. The fee depends on the pricing mode:

    • Based on allocated resources: You pay for the number of units of written data and resources allocated for data streaming.
    • Based on actual use:
      • If the DB operates in serverless mode, the data stream is charged under the YDB serverless mode pricing policy.

      • If the DB operates in dedicated instance mode, the data stream is not charged separately (you only pay for the DB, see the pricing policy).

    Learn more about the Data Streams pricing plans.

  • Transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

Getting startedGetting started

Set up your infrastructure:

Manually
Terraform
  1. Create a Managed Service for YDB database in any suitable configuration.

  2. Create a Managed Service for ClickHouse® cluster with any suitable configuration.

  3. Create a target endpoint:

    • Database type: ClickHouse.

    • Endpoint parameters:

      • Connection settings:

        • Connection type: Managed cluster.

          • Managed cluster: Select the source cluster from the list.
        • Database: Enter the database name.

        • User and Password: Enter the name and password of the user who has access to the database (for example, the database owner).

  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the data-transfer-yds-mch.tf configuration file to the same working directory.

    This file describes:

    • Database: Managed Service for YDB.
    • Service account with the yds.editor role.
    • Network.
    • Subnet.
    • Security group and rules required to connect to the Managed Service for ClickHouse® cluster from the internet.
    • Managed Service for ClickHouse® target cluster.
    • Target endpoint.
    • Transfer.
  6. Specify the following in the data-transfer-yds-mch.tf file:

    • folder_id: ID of the folder the resources will be created in.
    • sa_name: Name of the service account to be used in endpoints.
    • source_db_name: Managed Service for YDB database name.
    • target_db_name: ClickHouse® database name.
    • target_user and target_password: Username and password of the ClickHouse® database owner.
    • transfer_enabled: 0 to ensure that no transfer is created before a source endpoint is created manually.
  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    If there are any errors in the configuration files, Terraform will point them out.

  8. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Set up a Data Streams-enabled streamSet up a Data Streams-enabled stream

  1. Create a Data Streams data stream.
  2. Send test data to the data stream. Use data from the vehicle sensors in JSON format as a message:
{
    "device_id":"iv9a94th6rzt********",
    "datetime":"2022-06-05 17:27:00",
    "latitude":55.70329032,
    "longitude":37.65472196,
    "altitude":427.5,
    "speed":0,
    "battery_voltage":"23.5",
    "cabin_temperature":17,
    "fuel_level":null
}

Set up and activate the transferSet up and activate the transfer

Note

To rapidly deliver a large volume of data, use special endpoint settings.

  1. Create a source endpoint:

    • Database type: Yandex Data Streams.

    • Endpoint settings:

      • Connection settings:

        • Database: Select the Managed Service for YDB database from the list.
        • Stream: Specify the name of the Data Streams-enabled stream.
        • Service account: Select or create a service account with the yds.editor role.
      • Advanced settings:

        • Conversion rules: JSON.
        • Data scheme: You can specify a schema in two ways:
          • Field list.

            Set a list of topic fields manually:

            Name Type Key
            device_id STRING Yes
            datetime DATETIME
            latitude DOUBLE
            longitude DOUBLE
            altitude DOUBLE
            speed DOUBLE
            battery_voltage ANY
            cabin_temperature DOUBLE
            fuel_level ANY
          • JSON specification.

            Create and upload a json_schema.json data schema file in JSON format:

            json_schema.json
            [
                {
                    "name": "device_id",
                    "type": "string",
                    "key": true
                },
                {
                    "name": "datetime",
                    "type": "datetime"
                },
                {
                    "name": "latitude",
                    "type": "double"
                },
                {
                    "name": "longitude",
                    "type": "double"
                },
                {
                    "name": "altitude",
                    "type": "double"
                },
                {
                    "name": "speed",
                    "type": "double"
                },
                {
                    "name": "battery_voltage",
                    "type": "any"
                },
                {
                    "name": "cabin_temperature",
                    "type": "double"
                },
                {
                    "name": "fuel_level",
                    "type": "any"
                }
            ]
            
  2. Create a transfer:

    Manually
    Terraform
    1. Create a transfer of the Replication type that will use the created endpoints.
    2. Activate your transfer.
    1. In the data-transfer-yds-mch.tf file, specify these variables:

      • source_endpoint_id: ID of the source endpoint.
      • transfer_enabled: 1 to create a transfer.
    2. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

    3. Create the required infrastructure:

      1. Run this command to view the planned changes:

        terraform plan
        

        If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

      2. If everything looks correct, apply the changes:

        1. Run this command:

          terraform apply
          
        2. Confirm updating the resources.

        3. Wait for the operation to complete.

      Once created, your transfer will be activated automatically.

Test your transferTest your transfer

  1. Wait until the transfer status switches to Replicating.

  2. Send a new message to the data stream Data Streams:

    {
        "device_id":"rhibbh3y08qm********",
        "datetime":"2022-06-06 09:49:54",
        "latitude":55.71294467,
        "longitude":37.66542005,
        "altitude":429.13,
        "speed":55.5,
        "battery_voltage":null,
        "cabin_temperature":18,
        "fuel_level":32
    }
    
  3. Make sure the data from the Data Streams stream has been moved to the Managed Service for ClickHouse® cluster database:

    1. Connect to the Managed Service for ClickHouse® target cluster.
    2. Check that the ClickHouse® database contains a table with the name of the created Data Streams data stream with the same columns as the data schema in the source endpoint and the sent test data.

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources you created, deactivate the transfer.

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

  1. Delete the transfer.

  2. Delete the resources depending on how they were created:

    Manually
    Terraform
    • Delete the target endpoint.
    • Delete the Managed Service for YDB database.
    • Delete the Managed Service for ClickHouse® cluster.
    1. In the terminal window, go to the directory containing the infrastructure plan.

      Warning

      Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

    2. Delete resources:

      1. Run this command:

        terraform destroy
        
      2. Confirm deleting the resources and wait for the operation to complete.

      All the resources described in the Terraform manifests will be deleted.

  3. Delete the source endpoint.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Transferring data within microservice architectures
Next
Replicating logs to Object Storage using Fluent Bit
© 2025 Direct Cursus Technology L.L.C.