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
    • 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.
Tutorials
    • All tutorials
    • Deploying the Apache Kafka® web interface
    • Migrating a database from a third-party Apache Kafka® cluster to Managed Service for Apache Kafka®
    • Moving data between Managed Service for Apache Kafka® clusters using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for YDB to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for Greenplum® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for MongoDB using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for OpenSearch using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for PostgreSQL using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for YDB using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Data Streams using Data Transfer
    • Delivering data from Data Streams to Managed Service for YDB using Data Transfer
    • Delivering data from Data Streams to Managed Service for Apache Kafka® using Data Transfer
    • YDB change data capture and delivery to YDS
    • Configuring Kafka Connect to work with a Managed Service for Apache Kafka® cluster
    • Automating Query tasks with Managed Service for Apache Airflow™
    • Sending requests to the Yandex Cloud API via the Yandex Cloud Python SDK
    • Configuring an SMTP server to send e-mail notifications
    • Adding data to a ClickHouse® DB
    • Migrating data to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for ClickHouse® using Data Transfer
    • Asynchronously replicating data from PostgreSQL to ClickHouse®
    • Exchanging data between Managed Service for ClickHouse® and Yandex Data Processing
    • Configuring Managed Service for ClickHouse® for Graphite
    • Fetching data from Managed Service for Apache Kafka® to Managed Service for ClickHouse®
    • Fetching data from Managed Service for Apache Kafka® to ksqlDB
    • Fetching data from RabbitMQ to Managed Service for ClickHouse®
    • Saving a Data Streams data stream in Managed Service for ClickHouse®
    • Asynchronous replication of data from Yandex Metrica to ClickHouse® using Data Transfer
    • Using hybrid storage in Managed Service for ClickHouse®
    • Sharding Managed Service for ClickHouse® tables
    • Data resharding in a Managed Service for ClickHouse® cluster
    • Loading data from Yandex Direct to a data mart enabled by Managed Service for ClickHouse® using Cloud Functions, Object Storage, and Data Transfer
    • Loading data from Object Storage to Managed Service for ClickHouse® using Data Transfer
    • Migrating data with change of storage from Managed Service for OpenSearch to Managed Service for ClickHouse® using Data Transfer
    • Loading data from Managed Service for YDB to Managed Service for ClickHouse® using Data Transfer
    • Migrating databases from Google BigQuery to Managed Service for ClickHouse®
    • Configuring Cloud DNS to access a Managed Service for ClickHouse® cluster from other cloud networks
    • Migrating a Yandex Data Processing HDFS cluster to a different availability zone
    • Importing data from Managed Service for MySQL® to Yandex Data Processing using Sqoop
    • Importing data from Managed Service for PostgreSQL to Yandex Data Processing using Sqoop
    • Mounting Object Storage buckets to the file system of Yandex Data Processing hosts
    • Working with Apache Kafka® topics using Yandex Data Processing
    • Automating operations with Yandex Data Processing using Managed Service for Apache Airflow™
    • Shared use of Yandex Data Processing tables through Metastore
    • Transferring metadata between Yandex Data Processing clusters using Metastore
    • Importing data from Object Storage, processing and exporting to Managed Service for ClickHouse®
    • Migrating to Managed Service for Elasticsearch using snapshots
    • Migrating collections from a third-party MongoDB cluster to Managed Service for MongoDB
    • Migrating data to Managed Service for MongoDB
    • Migrating Managed Service for MongoDB cluster from 4.4 to 6.0
    • Sharding MongoDB collections
    • MongoDB performance analysis and tuning
    • Migrating a database from a third-party MySQL® cluster to a Managed Service for MySQL® cluster
    • Managed Service for MySQL® performance analysis and tuning
    • Syncing data from a third-party MySQL® cluster to Managed Service for MySQL® using Data Transfer
    • Migrating a database from Managed Service for MySQL® to a third-party MySQL® cluster
    • Migrating a database from Managed Service for MySQL® to Object Storage using Data Transfer
    • Migrating data from Object Storage to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Migrating a database from Managed Service for MySQL® to Managed Service for YDB using Data Transfer
    • MySQL® change data capture and delivery to YDS
    • Migrating data from Managed Service for MySQL® to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from AWS RDS for PostgreSQL to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from Managed Service for MySQL® to Managed Service for Greenplum® using Data Transfer
    • Configuring an index policy in Managed Service for OpenSearch
    • Migrating data from Elasticsearch to Managed Service for OpenSearch
    • Migrating data from a third-party OpenSearch cluster to Managed Service for OpenSearch using Data Transfer
    • Loading data from Managed Service for OpenSearch to Object Storage using Data Transfer
    • Migrating data from Managed Service for OpenSearch to Managed Service for YDB using Data Transfer
    • Copying data from Managed Service for OpenSearch to Managed Service for Greenplum® using Yandex Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Authenticating a Managed Service for OpenSearch cluster in OpenSearch Dashboards using Keycloak
    • Using the yandex-lemmer plugin in Managed Service for OpenSearch
    • Creating a PostgreSQL cluster for 1C:Enterprise
    • Searching for the Managed Service for PostgreSQL cluster performance issues
    • Managed Service for PostgreSQL performance analysis and tuning
    • Logical replication PostgreSQL
    • Migrating a database from a third-party PostgreSQL cluster to Managed Service for PostgreSQL
    • Migrating a database from Managed Service for PostgreSQL
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for YDB using Data Transfer
    • Migrating a database from Managed Service for PostgreSQL to Object Storage
    • Migrating data from Object Storage to Managed Service for PostgreSQL using Data Transfer
    • PostgreSQL change data capture and delivery to YDS
    • Migrating data from Managed Service for PostgreSQL to Managed Service for MySQL® using Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Troubleshooting string sorting issues in PostgreSQL after upgrading glibc
    • Migrating a database from Greenplum® to ClickHouse®
    • Migrating a database from Greenplum® to PostgreSQL
    • Exporting Greenplum® data to a cold storage in Object Storage
    • Loading data from Object Storage to Managed Service for Greenplum® using Data Transfer
    • Copying data from Managed Service for OpenSearch to Managed Service for Greenplum® using Yandex Data Transfer
    • Creating an external table from a Object Storage bucket table using a configuration file
    • Migrating a database from a third-party Valkey™ cluster to Yandex Managed Service for Valkey™
    • Using a Yandex Managed Service for Valkey™ cluster as a PHP session storage
    • Loading data from Object Storage to Managed Service for YDB using Data Transfer
    • Loading data from Managed Service for YDB to Object Storage using Data Transfer
    • Processing Audit Trails events
    • Processing Cloud Logging logs
    • Processing CDC Debezium streams
    • Analyzing data with Jupyter
    • Processing files with usage details in Yandex Cloud Billing
    • Entering data into storage systems
    • Smart log processing
    • Transferring data within microservice architectures
    • Migrating data to Object Storage using Data Transfer
    • Migrating data from a third-party Greenplum® or PostgreSQL cluster to Managed Service for Greenplum® using Data Transfer
    • Migrating Managed Service for MongoDB clusters
    • Migrating MySQL® clusters
    • Migrating to a third-party MySQL® cluster
    • Migrating PostgreSQL clusters
    • Creating a schema registry to deliver data in Debezium CDC format from Apache Kafka®

In this article:

  • Required paid resources
  • Getting started
  • Transfer your data from Yandex Direct to Object Storage using Cloud Functions
  • Transfer your data from Object Storage to Managed Service for ClickHouse® using Data Transfer
  • Delete the resources you created
  1. Building a data platform
  2. Loading data from Yandex Direct to a data mart enabled by Managed Service for ClickHouse® using Cloud Functions, Object Storage, and Data Transfer

Loading data from Yandex Direct to a Yandex Managed Service for ClickHouse® data mart using Yandex Cloud Functions, Yandex Object Storage, and Yandex Data Transfer

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Getting started
  • Transfer your data from Yandex Direct to Object Storage using Cloud Functions
  • Transfer your data from Object Storage to Managed Service for ClickHouse® using Data Transfer
  • Delete the resources you created

You can transfer data from Yandex Direct to Managed Service for ClickHouse® using Cloud Functions, Object Storage, and Data Transfer. Proceed as follows:

  1. Transfer your data from Yandex Direct to Object Storage using Cloud Functions.
  2. Transfer your data from Object Storage to Managed Service for ClickHouse® using Data Transfer.

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

Required paid resourcesRequired paid resources

The support cost includes:

  • Object Storage bucket fee: Storing data and performing operations with it (see Object Storage pricing).
  • Fee for function calls (see Yandex Cloud Functions pricing).
  • Secret storage and request fees (see Yandex Lockbox pricing).
  • 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 for cluster hosts (see Virtual Private Cloud pricing).

Getting startedGetting started

  1. Prepare the test data to load from Yandex Direct:

    1. Register the test application in Yandex.OAuth.

      Select Web services as the platform. In the Redirect URI field, paste the URL for debugging: https://oauth.yandex.ru/verification_code.

    2. Get a debug token for the application.

    3. Request test access to Yandex Direct for the application and wait for approval.

    4. Set up the sandbox in Yandex Direct with the Client role.

    5. (Optional) Check your setup by sending a request to the sandbox API from the application:

      Request example
      curl \
        --header 'Authorization: Bearer <debug_token>' \
        --header 'Accept-Language: en' \
        --data '
            {
              "method":"get",
              "params": {
                "SelectionCriteria": {},
                "FieldNames": [
                  "Id",
                  "Name"
                ]
              }
            }' \
        "https://api-sandbox.direct.yandex.com/json/v5/campaigns" | jq
      
      Response example
      {
        "result": {
          "Campaigns": [
            {
                "Id": 463476,
                "Name": "Test API Sandbox campaign 1"
            },
            {
                "Id": 463477,
                "Name": "Test API Sandbox campaign 2"
            },
            {
                "Id": 463478,
                "Name": "Test API Sandbox campaign 3"
            }
          ]
        }
      }
      
  2. Prepare your Yandex Cloud infrastructure:

    Manually
    Terraform
    1. Create a service account named storage-lockbox-sa and assign the storage.uploader and lockbox.payloadViewer roles to it.

    2. Create a static access key for the storage-lockbox-sa service account.

    3. Create a secret in Yandex Lockbox with three key:value pairs:

      • access_key:<public_key>
      • secret_key:<private_key>
      • app_token:<application_debug_token>
    4. Create a bucket in Object Storage.

    5. Create a Managed Service for ClickHouse® cluster in any suitable configuration with publicly available hosts.

    6. If using security groups in your Managed Service for ClickHouse® cluster, make sure they are configured correctly and allow connecting to the cluster.

    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 ya-direct-to-mch.tf configuration file to the same working directory.

      This file describes:

      • Network.
      • Subnet.
      • Security group and rules required to connect to a Managed Service for ClickHouse® cluster.
      • Service account with the storage.uploader and lockbox.payloadViewer roles.
      • Static key for the service account.
      • Yandex Lockbox secret.
      • Object Storage bucket.
      • Cloud Functions serverless function.
      • Managed Service for ClickHouse® target cluster.
      • Managed Service for ClickHouse® target endpoint.
      • Transfer.
    6. In the ya-direct-to-mch.tf file, specify these variables:

      • folder_id: Cloud folder ID, same as in the provider settings.
      • app_token: Application debug token.
      • bucket_name: Object Storage bucket name. The name must be unique within the service.
      • ch_password: Managed Service for ClickHouse® cluster admin user password.
    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.

Transfer your data from Yandex Direct to Object Storage using Cloud FunctionsTransfer your data from Yandex Direct to Object Storage using Cloud Functions

  1. Download the example-py.zip archive file with a Python function.

    The function uses an application token to read marketing campaign IDs and names from the sandbox, then writes this data to an Object Storage bucket in Parquet format.

    The function accepts the following input:

    • Service account key
    • Application token
    • Bucket name

    Tip

    You can use this function to obtain real campaign data or make requests on behalf of the agency. To do this, extract the archive file and uncomment all the required parameters in example.py. See the code comments for details.

  2. Create and configure a function in the Cloud Functions service:

    Manually
    Terraform
    1. Create a function.

    2. In the editor that opens, select Python as the runtime environment and clickContinue.

    3. Specify the required settings:

      • ZIP archive: ZIP archive.

      • File: Select the example-py.zip file you downloaded earlier.

      • Entry point: example.foo.

      • Service account: Select storage-lockbox-sa from the list.

      • Environment variables: Enter the bucket name in the key=value format:

        • Key: BUCKET.
        • Value: Name of the bucket created earlier (without the s3:// prefix).
      • Lockbox secrets: Specify the path to the three previously created Yandex Lockbox secrets as environment variables:

        • AWS_ACCESS_KEY_ID: access_key
        • AWS_SECRET_ACCESS_KEY: secret_key
        • TOKEN: app_token

      You can leave the other settings at their defaults.

    4. Click Save changes and wait for the function to compile.

    1. In the ya-direct-to-mch.tf file, specify these variables:

      • path_to_zip_cf: Path to the ZIP archive file with the function code.
      • create_function: 1 to create a function.
    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.

  3. Open the function you created in the management console. Select Functions in the left-hand panel.

  4. Click Run test and wait for the function to complete.

You will see a Parquet file in the bucket.

Transfer your data from Object Storage to Managed Service for ClickHouse® using Data TransferTransfer your data from Object Storage to Managed Service for ClickHouse® using Data Transfer

  1. Create a source endpoint with the following parameters:

    • Database type: Object Storage.

    • Bucket: Bucket name in Object Storage.

    • Access Key ID: Public part of the service account static key. You may copy it from the Yandex Lockbox secret.

    • Secret Access Key: Private part of the service account static key. You may copy it from the Yandex Lockbox secret.

    • Endpoint: https://storage.yandexcloud.net.

    • Region: ru-central1.

    • Data format: Parquet.

    • Schema: {"Id": "int64", "Name": "string"}.

    • Table: Name of the Parquet file in the bucket, e.g., ac05e4fe818e463f88a8a299d290734d.snappy.parquet.

    • Result table schema: Select Manual and specify field names and data types:

      • Id: Int64
      • Name: String

    For the other properties, leave the default values.

  2. Create an endpoint for the target and the transfer:

    Manually
    Terraform
    1. Create a Managed Service for ClickHouse® target endpoint using the parameters of the cluster you created earlier.

    2. Create a transfer that will use the created endpoints.

    1. In the ya-direct-to-mch.tf file, specify these variables:

      • source_endpoint_id: Source endpoint ID.
      • 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.

  3. Activate the transfer and wait until its status switches to Completed.

  4. Make sure the Object Storage source data was transferred to the Managed Service for ClickHouse® database:

    1. Connect to the cluster using clickhouse-client.

    2. Run this request:

      SELECT * FROM ac05e4fe818e463f88a8a299d290734d_snappy_parquet;
      

      Where ac05e4fe818e463f88a8a299d290734d is the Parquet file name.

      Response example
      ┌─────Id─┬─Name────────────────────────┬─__file_name─────────────────────────────────────┬─__row_index─┐
      │ 463476 │ Test API Sandbox campaign 1 │ ac05e4fe818e463f88a8a299d290734d.snappy.parquet │           1 │
      │ 463477 │ Test API Sandbox campaign 2 │ ac05e4fe818e463f88a8a299d290734d.snappy.parquet │           2 │
      │ 463478 │ Test API Sandbox campaign 3 │ ac05e4fe818e463f88a8a299d290734d.snappy.parquet │           3 │
      └────────┴─────────────────────────────┴─────────────────────────────────────────────────┴─────────────┘
      

Delete the resources you createdDelete the resources you created

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 source endpoint.
  3. Delete the objects from the bucket.

Delete the other resources depending on how they were created:

Manually
Terraform
  • Target endpoint.
  • Managed Service for ClickHouse® cluster.
  • Object Storage bucket.
  • Function.
  • Secret in Yandex Lockbox.
  • Service account.
  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.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Data resharding in a Managed Service for ClickHouse® cluster
Next
Loading data from Object Storage to Managed Service for ClickHouse® using Data Transfer
© 2025 Direct Cursus Technology L.L.C.