Article
AWS Transform continuous modernization is now generally available
The AWS DevOps Blog announced on August 3, 2026 that AWS Transform continuous modernization is generally available in AWS Transform supported Regions. The practical change is that repository analysis, technical-debt findings, pull-request remediation, and recurring runs can be managed through the web app and CLI.
Share
Koharu's reading tip
The useful reading angle is less “AI fixes code” and more how source connections, analysis types, remediation PRs, recurring runs, and pricing checks fit into operations. Permissions and cost boundaries matter before rolling it across a portfolio.

AWS Transform continuous modernization moves to general availability
The AWS DevOps Blog announced on August 3, 2026 that AWS Transform continuous modernization is generally available in AWS Transform supported Regions. AWS What's New introduced the capability as a Preview on June 15, 2026, initially available in US East (N. Virginia) and Europe (Frankfurt). The primary source is therefore the GA update from that Preview phase.
For AWS Transform Regions, the official Supported Regions for AWS Transform page describes where AWS Transform workspaces can be created. Because the primary source says the capability is generally available in AWS Transform supported Regions, teams should check that Region list together with the Regions enabled in their own AWS accounts before adoption.
Repository analysis and remediation PRs become a continuous workflow
According to the primary source, AWS Transform continuous modernization connects to source control systems such as GitHub, GitLab, Bitbucket, and local repositories, scans repositories, and generates prioritized findings. At the user's direction, it can autonomously create pull requests with validated code changes.
The official user guide describes the capability as analysis and remediation for source code repositories, and says work runs in the customer's AWS account using the customer's credentials. The AWS Transform continuous modernization user guide is the supporting source for these mechanics. This is best read less as a one-time modernization request and more as a way to keep finding and remediating technical debt over time.
koharu tone="tip" portrait="characters/deformed/confident-smile.webp" General availability does not mean every repository has to be onboarded at once. Start with a narrow repository set and clear permissions, then decide who reviews the generated PRs.
Analysis types cover technical debt, security, and agent readiness
The primary source lists Rapid tech debt analysis, Comprehensive tech debt analysis, Security analysis, Agentic readiness, Modernization readiness, and Custom analysis. The official documentation describes tech-debt-quick as a fast metadata scan of manifests such as pom.xml, package.json, and requirements.txt, while tech-debt-comprehensive performs deeper code-level analysis.
The same documentation describes security as vulnerability and insecure-coding-pattern detection through AWS Security Agent, agentic-readiness as a 56-criterion assessment across five categories, and modernization-readiness as an evaluation of opportunities such as containerization and serverless migration. The word security appears here, but the primary source is not a CVE advisory or urgent response notice. That is why this draft treats the item as a feature update rather than a security advisory.
The web app handles source connection, recurring analysis, and remediation creation
The primary source says the AWS Transform web application can now connect an SCM provider, start analyses, schedule recurring analyses, review findings, and create remediations. The official Working with continuous modernization page organizes the workflow around source management, repository discovery, analysis, findings, and remediation.
Operationally, this is more than a new dashboard. It gives teams a place to manage repository inventory, run analyses, process findings, generate remediation PRs, and schedule recurring scans. For multi-team portfolios, labels and scoped target sets become important because they determine how analysis and remediation work are grouped.
CLI and developer tools connect the workflow to IDEs and batch execution
The primary source says the updated AWS Transform CLI atx ct and atx ct remote subcommands add support for scheduled analyses and remediations using Amazon EC2 and AWS Batch. It also says the AWS Transform Kiro power and plugin make repository configuration and analyses easier from an IDE or terminal.
The official developer-tools documentation says Kiro IDE users can install the AWS Transform Kiro Power, while Claude Code, Codex, and Cursor users can use awslabs/agent-plugins under plugins/aws-transform. The Developer tools page lists agent skills such as Source, Discovery, Analysis, Findings, Remediation, EC2 Execution, Batch Execution, Schedule, and Reporting, along with the atx ct command surface.
Region, permissions, and pricing deserve a check before rollout
Before adoption, Region and data-processing behavior are worth reviewing. The AWS Transform Regions documentation notes that data may be processed in a different Region from the Region where AWS Transform is used, and points readers to cross-region processing and data protection details. Because this capability connects to source code repositories, that belongs in the security review.
Pricing also needs a current check. The AWS Transform pricing page lists AWS Transform continuous modernization as a paid feature. It also still contains wording about Public Preview billing and a separate pricing announcement at GA, so after the August 3, 2026 GA announcement, teams should verify the billing terms before deciding scan frequency and repository scope.
Source
- Title: Analyze and remediate technical debt autonomously with AWS Transform – continuous modernization
- URL: https://aws.amazon.com/blogs/devops/analyze-and-remediate-technical-debt-autonomously-with-aws-transform-continuous-modernization/
Share
Related Articles
These articles share nearby categories or tags, so you can keep reading along the same thread.




