Load AWS Transcribe data to DuckDB

Amazon Transcribe is an automated speech recognition service that converts speech to text for various applications. Everything needed to build a working AWS Transcribe → 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 AWS Transcribe 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 AWS Transcribe 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 AWS Transcribe 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.

---

AWS Transcribe API at a glance

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

---

How do I authenticate with the AWS Transcribe API?

Amazon Transcribe uses AWS Signature Version 4 (SigV4). Requests must be signed using the HMAC-SHA256 algorithm and include an 'Authorization' header containing the credentials, signature, and scope.

1. Get your credentials

1. Sign in to the AWS Management Console and navigate to the IAM (Identity and Access Management) dashboard. 2. In the navigation pane, select Users. 3. Click the user name you wish to use for programmatic access. 4. Select the Security credentials tab. 5. Under the Access keys section, click Create access key. 6. Select the appropriate use case (e.g., Local code or Command Line Interface) and proceed through the prompts. 7. Download the .csv file containing the Access Key ID and Secret Access Key immediately, as you cannot view the secret key again.

2. Add them to .dlt/secrets.toml

Copy
[sources.aws_transcribe_source]
aws_access_key_id = "YOUR_ACCESS_KEY_ID"
aws_secret_access_key = "YOUR_SECRET_ACCESS_KEY"
aws_region = "us-east-1"

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 AWS Transcribe data can I load into DuckDB?

These are the AWS Transcribe endpoints dlt can load into DuckDB:

---

How do I load only new AWS Transcribe records?

AWS Transcribe exposes NextToken on /, 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": "transcription_jobs", "endpoint": {
    "path": "/",
    "data_selector": "TranscriptionJobSummaries",
    "incremental": {"cursor_path": "NextToken", "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 AWS Transcribe pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading transcription_jobs and vocabularies from the AWS Transcribe API into DuckDB:

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

@dlt.source
def aws_transcribe_source(aws_access_key_id_aws_secret_access_key_aws_session_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://transcribe.{region}.amazonaws.com",
            "auth": {"type": "api_key", "api_key": aws_access_key_id_aws_secret_access_key_aws_session_token, "name": "Authorization", "location": "header"},
        },
        "resources": [
            {"name": "transcription_jobs", "endpoint": {"path": "/", "data_selector": "TranscriptionJobSummaries"}},
            {"name": "medical_transcription_jobs", "endpoint": {"path": "/", "data_selector": "MedicalTranscriptionJobSummaries"}}
        ],
    }
    yield from rest_api_resources(config)


def load_aws_transcribe_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="aws_transcribe_pipeline",
        destination="duckdb",
        dataset_name="aws_transcribe_data",
    )
    load_info = pipeline.run(aws_transcribe_source())
    print(load_info)


if __name__ == "__main__":
    load_aws_transcribe_to_duckdb()

Run it with python aws_transcribe_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 AWS Transcribe 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("aws_transcribe_pipeline").dataset()
df = data.transcription_jobs.df()
print(df.head())

SQL:

Copy
SELECT * FROM aws_transcribe_data.transcription_jobs LIMIT 10;

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

---

How do I deploy the AWS Transcribe 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 AWS Transcribe 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 AWS Transcribe 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