Data engineering and DBA teams managing complex warehouses run hundreds of SQL operations daily. Without a dedicated orchestration layer, this creates brittle, invisible failure points.
Built on a serverless AWS stack — no servers to manage, no agents to maintain, no vendor lock-in beyond what you're already running.
%YEARMONTH%, %PREVMONTH%, %DAYOFWEEK%, %PREVIOUS_START_DT%, and more. Pass results between queries using %PREV_VALUE%.Native executors for each database type — each tuned to the right access pattern, authentication method, and AWS API.
next_run < now. Each due activity triggers a Step Functions execution.From monthly materialized view pipelines to incremental ETL loads — real patterns used in production by Cloudwalker clients.
mv_sales_%YEARMONTH%), refreshes the previous month's MV, and reconstructs the UNION view that joins all monthly data — all with conditional execution to check object existence before acting.%PREVIOUS_START_DT%, queries automatically process only new data since the last successful execution. No manual watermark table, no hardcoded dates — the system tracks the last run and injects the correct timestamp into every query.expected_duration alerts fire immediately if any activity starts running longer than baseline.Dynamic values resolved at execution time — no hardcoded dates, no manual watermark tracking. Use them in SQL queries or global parameters.
| Keyword | Format | Example (2026-04-15) | Description |
|---|---|---|---|
%YEARMONTH% | YYYYMM | 202604 | Current year and month |
%PREVYEARMONTH% | YYYYMM | 202603 | Previous year and month |
%NEXTYEARMONTH% | YYYYMM | 202605 | Next year and month |
%YEAR% | YYYY | 2026 | Current year |
%MONTH% | MM | 04 | Current month |
%PREVMONTH% | MM | 03 | Previous month number |
%DAY% | DD | 15 | Current day of month |
%DAYOFWEEK% | 1–7 | 3 | ISO day of week (Mon=1, Sun=7) |
%PREVIOUS_START_DT% | datetime+tz | 2026-04-14 00:15:00 +02:00 | Start timestamp of last successful run |
%PREVIOUS_END_DT% | datetime+tz | 2026-04-14 00:17:32 +02:00 | End timestamp of last successful run |
%PREV_VALUE% | string | 1 | Result of last returns: true query |
%PREV_VALUE@N% | string | — | Result of query with order_num = N |
%PREV_VALUE$name% | string | — | Result of query with the given name |
Cloudwalker handles infrastructure and access provisioning. Your team handles AWS-side setup and activity creation. Both workstreams run in parallel.
CREATED status, test query executes, email notification arrives
No servers to patch, no daemons to monitor. SQL Query Orchestrator runs entirely on AWS managed services — deployed via CloudFormation in your account.
condition field — a Python expression evaluated using the simpleeval library. The most common pattern: query 1 checks whether an object exists (returns 0 or 1), query 2 has condition %PREV_VALUE% != 0. If the condition is false, the query is skipped without error.abort_on_error: true, the activity stops at the first failed query, stores the error in DynamoDB, and sends a failure notification email. With abort_on_error: false, the error is logged and execution continues with the next query.returns: true stores the first column of the first result row. Subsequent queries reference it via %PREV_VALUE% (last result), %PREV_VALUE@3% (query by order_num), or %PREV_VALUE$query_name% (query by name).retention_result field (in months). DynamoDB TTL automatically deletes older records. S3 log files can have additional lifecycle policies applied at the bucket level.SQL Query Orchestrator automates the repetitive SQL operations your team runs every day — with visibility, notifications, and zero infrastructure overhead.
Request a demo