AWS Transform Custom · Generally Available

Crush Tech Debt with
Agentic AI

Transform any code pattern — version upgrades, SDK migrations, framework transitions, and custom transformations. Powered by AI agents that learn, adapt, and scale.

5×
Faster Transformations
128
Parallel Repos
12+
Built-in TDs
913
Repos Transformed
01

The Problem: Tech Debt at Scale

70% of Fortune 500 legacy code is 20+ years old. Manual migration is slow, error-prone, and doesn't scale.

Complex Legacy Systems

Outdated frameworks, deprecated APIs, end-of-life runtimes. Every delay increases security risk and maintenance cost.

Labor-Intensive Process

Manual code analysis, dependency mapping, refactoring — each repo takes days or weeks of skilled developer time.

Limited Scalability

One repo at a time. 500 repos to upgrade? That's years of work with traditional approaches.

Knowledge Silos

Migration expertise lives in a few engineers' heads. When they leave, the knowledge goes with them.

02

How the Custom Transformation Agent Works

A four-phase workflow: Define → Pilot → Scale → Monitor. The agent improves from every execution through continual learning.

Define

Natural language + docs + samples

SKILL.md format. Draft → Publish to registry.

Execute

Local or 128 parallel on Fargate

CLI, Kiro IDE, or Web Console.

Verify

Build + test + self-debug

Iterates until validation passes.

Learn

Knowledge items extracted

Owner approves KIs for future runs.

Transformation Patterns & Complexity

From low-effort version upgrades to high-complexity cross-language migrations — all driven by natural language

Language Version Upgrades (Low–Med)
Java 8/11 → 17/21 Python 3.8 → 3.13 Node.js 12 → 22 TypeScript upgrades Java 8 → 26 Lambda runtime EOL
API & Service Migrations (Medium)
AWS SDK v1 → v2 (Java) AWS SDK v2 → v3 (JS) Boto2 → Boto3 JUnit 4 → 5 javax → jakarta
Framework & Library Upgrades (Medium)
Spring Boot 2 → 3 React 17 → 18 Log4j 1 → 2 CDK v1 → v2 Django upgrades JBoss → Spring Boot Log4J → SLF4J
Advanced Patterns (High–Very High)
Angular → React x86 → Graviton (ARM) Python → TypeScript CDK → Terraform C → Rust COBOL → Java + Any Custom Pattern

Continuous Modernization

GA

Beyond one-off transformations, AWS Transform can watch your whole portfolio. Connect GitHub, GitLab, or Bitbucket, then run analyses on demand or on a schedule to surface and prioritize tech debt. For findings that have a fix, it opens pull or merge requests with validated code changes for review. Analysis and remediation run in your own AWS account using your credentials — your source code stays under your control.

Modernization Analysis (MODA)

Scans code for cloud-native maturity gaps and maps findings to AWS modernization pathways. Completes in about 5–30 minutes per repository.

Agentic Readiness Analysis (ARA)

Evaluates whether a system is ready to be safely called by AI agents — covering APIs, identity, state management, human-in-the-loop controls, and observability.

03

See the Transformation in Action

Watch Java 8 code transform into modern Java 21 — character by character.

● Before (Java 8)
● After (Java 21)
04

Race the Clock: Manual vs Transform

Pick your repo count, hit Start, and watch the time difference unfold.

Assumes 80% time reduction with AWS Transform (reported by customers). Adjust dev-days to match your environment.

Manual Migration Sequential
0 dev-weeks
AWS Transform 128 parallel
0 dev-weeks
↔ 128 concurrent streams
—
Manual time
—
Transform time
—
Time saved
05

Pricing: What's Free, What's Paid

Most AWS Transform agents are free. Custom transformations are billed per agent minute — only when the agent is actively working on your code. AWS-managed .NET transformations now run free up to 50,000 agent minutes a month.

✓ Free Agents

AgentCost
AssessmentFree
VMware migrationFree
Windows modernizationFree
Mainframe modernizationFree
AWS-managed .NET transformation newFree*
50,000agent minutes / month

The AWS-managed AWS/dotnet-modernization transformation runs at no charge up to 50,000 agent minutes per month — enough for a ~500,000-line .NET Framework port (~25,000 agent minutes) with room to spare. Unused minutes do not roll over.

Standard AWS infrastructure charges apply for resources created during migration (EC2, RDS, etc.).

Where It Runs

The migration and modernization agents are available in all AWS commercial regions. AWS Transform custom started in US East (N. Virginia) and has since expanded to eight regions — adding Europe (Frankfurt, London), Asia Pacific (Mumbai, Tokyo, Seoul, Sydney), and Canada (Central).

us-east-1 eu-central-1 eu-west-2 ap-south-1 ap-northeast-1 ap-northeast-2 ap-southeast-2 ca-central-1

Region coverage changes often — confirm against the supported regions page before you plan a rollout.

Custom Transformation Agent

$0.035
per agent minute
What's billedIncluded?
Agent planning & reasoning
Code analysis & modification
Local builds & test runsNot billed
User idle timeNot billed
Continual learningIncluded
Campaign managementIncluded
Continuous modernization analyses new
Continuous modernization remediations new

Continuous modernization runs on the same custom agent, so each repo analysed and each remediation is billed in agent minutes. Security analyses are the exception — those are charged by AWS Security Agent, not in agent minutes.

Real-World Cost Examples

Node.js SDK Upgrade
~3,000 lines of code
$0.70
~20 agent minutes
Java Version Upgrade
~17,000 lines of code
$2.52
~72 agent minutes
Python Runtime Upgrade
~4,000 lines of code
$1.30
~37 agent minutes
AWS-managed .NET new
~500,000 lines of code
$0.00
~25,000 agent minutes — within the free monthly quota
Tip: Costs vary by codebase complexity, not just size. Run a few pilot repos to establish your baseline, then use AWS Budgets to set spend limits. You can pause or stop any transformation at any time — billing stops immediately.
06

Sample Transformation Runs

Real migrations executed by AWS Transform Custom — explore the full worklog, code changes, and validation results.

Get Started with AWS Transform Custom

Install the Kiro IDE extension or use the ATX CLI to start transforming today.

curl -fsSL https://transform-cli.awsstatic.com/install.sh | bash
07

Frequently Asked Questions

Key details from the official AWS Transform FAQ — covering capabilities, security, and scale.

90%
Efficacy rate for Node.js upgrades
Air Canada
80%
Reduction in time and costs
Air Canada
70%
Acceleration per app migration
Twitch (913 repos)
2,876
Developer days saved
Twitch (≈11 dev years)
90%
Timeline reduction
Coupang (70+ Java apps)
60–75%
Timeline reduction
The Gnar Company
+ What types of transformations does AWS Transform Custom support?
AWS Transform Custom supports 10 transformation pattern categories with varying complexity:
  • Language Version Upgrades (Low–Med) — Java 8→21, Python 3.8→3.13, Node.js 12→22
  • API & Service Migrations (Medium) — AWS SDK v1→v2, Boto2→Boto3, JUnit 4→5, javax→jakarta
  • Framework Upgrades (Medium) — Spring Boot 2→3, React 17→18, Django upgrades
  • Framework Migrations (High) — Angular→React, Redux→Zustand, Vue→React
  • Library & Dependency Upgrades (Low–Med) — Pandas 1→2, NumPy, Lodash upgrades
  • Code Refactoring & Pattern Modernization (Low–Med) — Print→logging, f-strings, type hints, observability
  • Script & File Translations (Low–Med) — CDK→Terraform, Terraform→CloudFormation, Bash→PowerShell
  • Architecture Migrations (Med–High) — x86→Graviton (ARM), on-prem→Lambda, server→containers
  • Language-to-Language Migrations (Very High) — Java→Python, JS→TypeScript, Python→Go
  • Custom & Organization-Specific (Varies) — Internal library migrations, org coding standards, proprietary frameworks
A transformation definition (TD) is represented as a SKILL.md file with optional references/ folder. Create via natural language in interactive mode, save as draft, then publish to your account's registry.
+ How does the agent learn and improve over time?
AWS Transform Custom uses two types of knowledge: References and Knowledge Items.
  • References — User-provided documentation stored in the TD's references/ folder. Migration guides, API specs, code samples (max 10MB total). Loaded as needed during execution.
  • Knowledge Items (KIs) — Automatically extracted learnings from transformation executions. Created asynchronously by the continual learning system based on execution trajectories, developer feedback, and code fixes encountered.
KIs start in a "not approved" state and must be explicitly approved by transformation owners before they influence future runs. The learning process occurs automatically after transformations complete — no additional input required. KIs are transformation-specific and not shared across accounts.
+ What interfaces are available — CLI, IDE, or web?
AWS Transform Custom operates through multiple surfaces:
  • ATX CLI — atx custom for interactive mode, atx custom def exec for autonomous execution. Supports --trust-all-tools for fully unattended runs. Scriptable into CI/CD pipelines.
  • Kiro IDE — The AWS Transform Power provides an integrated experience with real-time progress, code diffs, and inline verification. Human-in-the-loop feedback built in.
  • Web Console — Manages large-scale campaigns across multiple repositories with team collaboration and progress tracking.
  • MCP/A2A Gateway — Accessible from Claude Code, GitHub Copilot, or any MCP-compatible tool. Data stays centralized.
Key CLI commands: atx custom def list (registry), atx custom def save-draft (save WIP), atx custom def publish (share with team), atx custom def list-ki (view knowledge items).
+ How does verification work after a transformation?
After transformation, the agent runs an AI-led evaluation loop to auto-remediate build errors. User-defined validation steps can include:
  • Automated builds — full compile/build to catch errors
  • Unit test execution — runs existing tests to verify functional equivalence
  • Human code reviews — transformed code is committed to a new branch for review
  • Custom validation scripts — any verification you define in the transformation plan
If transformed code fails validation, it's sent back to the agent to fix or flagged for further review. The agent self-corrects — this debugging loop is often the most impressive part of a live demo.
+ Is my source code secure during transformation?
Yes. AWS Transform is designed with security as a priority:
  • Source code is processed in a network-isolated execution environment
  • Code is stored only for the duration of the job and purged after completion
  • Supports customer-managed KMS keys for encryption
  • All data encrypted in transit
  • You own the transformed code — AWS Transform does not retain any copy after committing to your branch
For CLI-based local transformations, your code never leaves your machine — the agent runs locally.
+ How does it scale to hundreds of repositories?
AWS Transform Custom scales from 1 repo locally to 128 in parallel on Fargate. The web experience manages large-scale campaigns:
  • Define once — create a transformation definition with exit criteria
  • Execute at scale — autonomous mode processes repos in parallel
  • Track centrally — web dashboard shows progress across all repos
  • Learn globally — knowledge items from one repo improve all subsequent ones
Coupang transformed 70+ Java applications in 2 months with just 5 developers. Twitch is projecting savings of 2,876 developer days across 913 repositories.
+ What does pricing look like?
Assessment, VMware, Windows, and Mainframe agents are free. Custom transformations are billed at $0.035 per agent minute — only when the agent is actively working on your code (not during builds, tests, or idle time). Real-world examples:
  • Node.js SDK upgrade: ~$0.70 per repo
  • Java 8→21 upgrade: ~$2.52 per repo
  • Python version upgrade: ~$1.30 per repo
At scale, even 100 Java repos would cost approximately $252 in agent time — compared to months of developer effort.