AWS Transform – continuous modernization (preview) is a new AWS capability designed to autonomously analyze and remediate technical debt across large-scale codebases. According to Amazon Web Services, the tool scans repositories against configurable baselines to identify deprecated frameworks and end-of-life dependencies, then automatically generates pull requests to apply the necessary fixes.
Automating Technical Debt Remediation at Scale
Engineering organizations often spend up to 30% of their IT budgets managing technical debt, according to AWS. This overhead typically stems from a fragmented toolchain where separate utilities handle dependency issues, vulnerabilities, and code quality. AWS Transform aims to consolidate these functions into a single workflow that detects, prioritizes, and fixes code regressions continuously.
The “continuous modernization” preview addresses the acceleration of technical debt caused by AI-assisted development. As coding agents increase the volume of code produced, the pace of change often outstrips a developer’s ability to maintain libraries and runtimes manually. AWS Transform automates this by scanning repositories in hours rather than weeks, providing a “ground truth” view of a codebase’s state regardless of manual team reports.
Continuous Analysis and Autonomous Fixes
AWS Transform operates using a baseline-driven approach. Out of the box, the system includes policies to detect common sources of debt, such as outdated Java versions or deprecated frameworks. Platform teams can also codify internal standards—such as preferred logging patterns or approved internal libraries—and apply them across thousands of repositories.
Once a deficiency is identified, the tool handles remediation through two primary mechanisms:
- Autonomous Pull Requests: For common scenarios like SDK migrations or library updates, AWS Transform generates a pull request (PR) and notifies the owning team. Teams can merge the PR or implement their own fix; the system detects the resolution automatically.
- Security Integration: The tool integrates with the AWS Security Agent to pull security vulnerabilities into the same prioritized list as general technical debt, streamlining the patching process.
Comparing Continuous Mode vs. Campaign Mode
AWS Transform provides two distinct operational paths depending on the scope of the modernization effort. While continuous modernization handles the “day-to-day” maintenance, campaign mode is reserved for high-impact architectural shifts.
| Feature | Continuous Mode | Campaign Mode |
|---|---|---|
| Primary Goal | Recurring maintenance and hygiene | Large-scale project migration |
| Typical Use Case | Security patches, library updates | Framework shifts, major runtime upgrades |
| Scope | Ongoing, high-volume updates | Targeted, project-based efforts |
Deployment and Availability
AWS Transform – continuous modernization (preview) is available now. Users can access the service through the AWS Transform web application or the AWS Transform Kiro Power. For organizations utilizing coding agents, the tool offers integration via MCP (Model Context Protocol) and specific skills to embed remediation workflows directly into the development environment.
Frequently Asked Questions
Does AWS Transform force changes into my code?
No. The tool generates pull requests. Engineering teams retain control and must review and merge the PRs before any changes are applied to the codebase.
Can I create my own rules for what constitutes “tech debt”?
Yes. Beyond the default policies for end-of-life dependencies, organizations can define custom remediation patterns based on their own internal coding standards and approved libraries.
Related reading