Terminal
Terminal/Skill
Guides a Teradata to Amazon Redshift migration, converting schemas, SQL, and stored procedures, then validating data and performance.
By Amazon Web Services
Works with
npx skills add aws/agent-toolkit-for-aws --skill migrating-to-amazon-redshiftThis skill is AI guidance, not an execution framework. It is entirely Markdown knowledge (rules, mappings, patterns, best practices) — no executable code. All execution — conversion, the discovery/migration/validation runners, dependencies, and infrastructure — you (the AI) generate at runtime from this knowledge, tailored to the customer's environment.
Principle: knowledge over shipped code → less drift, nothing for the customer to run or depend on, reliable first-time results. Do not look for a pyproject, a tools package, an orchestrator engine, or shipped scripts — there are none by design; you generate execution.
Runtime: this skill works with or without the AWS MCP server — step guidance uses AWS CLI syntax. Running it with the AWS MCP server is recommended for sandboxed execution and audit logging; without it, the AI runs the generated scripts on the host shell (assumes Bash, Python 3, and AWS CLI + credentials). Do not assume MCP-only tools are available.
This skill migrates a supported source data warehouse to Amazon Redshift. First identify the
source system, then load that source's knowledge under references/<source>/:
references/teradata/ — supported (all references below).references/<source>/ set when ready.The workflow is source-agnostic (discovery → convert → migrate → validate → performance → report); only the conversion knowledge is source-specific. Everything below is the Teradata set.
BEGIN/REPLACE QUERY LOGGING). If DBQL is
empty, mark it unavailable and fall back to always-on DBC.AMPUsageV — see
references/teradata/discovery-queries.md.references/ to reason and
convert — apply the rules in references/teradata/conversion-rules.md directly for conversion, and
generate the discovery/migration/validation runners (and the read-only discovery collector
from references/teradata/discovery-queries.md) tailored to the environment.teradatasql, boto3, …) is
pip install-ed on demand by that script / its run-instructions — pin exact versions.
Teradata TTU (BTEQ/TPT) is Linux/Windows-only — not macOS; prefer WRITE_NOS +
teradatasql (cross-platform, no client) for discovery/extract unless a TTU/Linux host exists..env file or profile may
be used — never commit it. Never hard-code or echo secrets. In a portable
bundle, reference a co-located credentials file and ship a credentials.env.example template — the
real file is git-ignored.output/ in the
user's working dir; keep output/state.md current so work is resumable.Run in order; each phase's result/ feeds the next (see references/teradata/orchestration.md).
references/teradata/discovery-queries.md (read-only collection SQL + BTEQ driver template the AI generates) → output/discovery/result/inventory.jsonreferences/teradata/conversion-rules.md, references/teradata/data-type-mapping.md,
references/teradata/architecture-mapping.md, references/teradata/stored-procedure-migration.md,
references/teradata/bteq-to-rsql.md, references/teradata/common-errors.mdreferences/teradata/data-migration-patterns.mdreferences/teradata/validation-patterns.mdreferences/teradata/performance.md, references/teradata/sizing.mdreferences/teradata/reporting.mdThere is no converter to run — convert by applying the rules in
references/teradata/conversion-rules.md directly (with the type / architecture / stored-procedure /
BTEQ references): apply the deterministic rules to the well-understood bulk, flag the
manual-rewrite constructs with their suggested rewrites, assign a confidence per object,
and fix any Redshift errors using references/teradata/common-errors.md. The reference docs are the
single source of truth; conversion-rules.md includes golden input→output examples to match.
output/<phase>/
(script + co-located credentials template + relative result/ + run-instructions.md); the
operator runs it on a reachable host and copies result/ back. The copied-back result/ is
the durable state — read it (+ state.md) and continue.<project-workspace>/
migration-config.yaml # operator-authored: endpoints, scope, strategy
.gitignore # ignores output/
output/ # everything generated (git-ignored)
state.md # progress cursor
discovery/ … result/inventory.json
conversion/ … result/{ddl,sql,procedures,rsql}/ manual_review.json
data_migration/ … result/{extract,load,templates}/ migration_manifest.json
validation/ … result/validation_report.json
performance/ … result/{perf_baseline,perf_compare}.json
reporting/ result/migration_report.md
*.example templates).COPY … IAM_ROLE (not access
keys). Enable encryption on the target Redshift cluster.output/… (manifests, reports, state.md) MUST
NOT embed credentials or endpoints beyond what the operator supplies in migration-config.yaml.IAM_ROLE hardening. Scope the role's policy to the specific staging prefix (not
bucket-wide s3:*), and include condition keys in its trust policy (aws:SourceAccount /
aws:SourceArn, or sts:ExternalId for cross-account) to prevent confused-deputy assumption —
per Redshift IAM-role authorization best practices.The AWS MCP server (recommended runtime) additionally provides sandboxed execution and audit logging for the generated scripts.
| File | Topic |
|---|---|
references/teradata/orchestration.md | phase workflow + state model |
references/teradata/conversion-rules.md | the 72 conversion rules (source of truth) |
references/teradata/data-type-mapping.md | TD→RS type mapping |
references/teradata/architecture-mapping.md | PI→DISTKEY, PPI→SORTKEY, Join Index→MV |
references/teradata/stored-procedure-migration.md | SP → PL/pgSQL |
references/teradata/bteq-to-rsql.md | BTEQ → RSQL |
references/teradata/common-errors.md | common Redshift errors + fixes |
references/teradata/discovery-queries.md | DBC system-view inventory queries |
references/teradata/data-migration-patterns.md | COPY/TPT/micro-batch/checkpoint |
references/teradata/validation-patterns.md | row-count/aggregate/sample compare |
references/teradata/performance.md | representative-query extraction + compare |
references/teradata/sizing.md | RG node type + count from the source profile |
references/teradata/reporting.md | migration status-report generation |