Load VK Cloud data to DuckDB

VK Cloud provides a suite of REST APIs for managing cloud services like virtual machines, storage, and networking using OpenStack-based infrastructure. Everything needed to build a working VK Cloud → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your VK Cloud to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from VK Cloud to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the VK Cloud API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

VK Cloud API at a glance

These values come from the VK Cloud API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the VK Cloud API?

Authentication requires an OpenStack Keystone token passed in the 'X-Auth-Token' header. The 'Accept: application/json' header is also typically required for REST API requests.

1. Get your credentials

1. Log in to your VK Cloud management console. 2. Enable API access: Click your username in the header, go to Project settings or Account settings (Security tab), and enable API access. 3. Navigate to the API access tab within your Project settings to view your credentials. 4. VK Cloud uses Keystone tokens for authentication. You can generate or view a token on the API access page; copy the token value to use in your API headers (e.g., as 'X-Auth-Token'). Note that the Project ID, required for many API endpoints, is also found on the API access or Terraform tabs in the Project settings page.

2. Add them to .dlt/secrets.toml

Copy
[sources.vk_cloud_source]
keystone_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What VK Cloud data can I load into DuckDB?

These are the VK Cloud endpoints dlt can load into DuckDB:

---

How do I load only new VK Cloud records?

VK Cloud exposes updated_at on /v2.1/servers, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "servers", "endpoint": {
    "path": "/v2.1/servers",
    "data_selector": "servers",
    "incremental": {"cursor_path": "updated_at", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated VK Cloud pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading Nova (for virtual machines) and Cinder (for block storage) from the VK Cloud API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def vk_cloud_source(keystone_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "The base URL is region- and service-specific; consult the API Endpoints section in the VK Cloud management console for the required endpoint address.",
            "auth": {"type": "bearer", "token": keystone_token},
        },
        "resources": [
            {"name": "servers", "endpoint": {"path": "/v2.1/servers", "data_selector": "servers"}},
            {"name": "images", "endpoint": {"path": "/v2/images", "data_selector": "images"}}
        ],
    }
    yield from rest_api_resources(config)


def load_vk_cloud_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="vk_cloud_pipeline",
        destination="duckdb",
        dataset_name="vk_cloud_data",
    )
    load_info = pipeline.run(vk_cloud_source())
    print(load_info)


if __name__ == "__main__":
    load_vk_cloud_to_duckdb()

Run it with python vk_cloud_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query VK Cloud data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("vk_cloud_pipeline").dataset()
df = data.servers.df()
print(df.head())

SQL:

Copy
SELECT * FROM vk_cloud_data.servers LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the VK Cloud to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw VK Cloud loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load VK Cloud data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack