Home
    /
    Digital Tools

    AWS Transform Continuous Modernization Reaches General Availability with Automated Pull RequestsAWS Transform Continuous Modernization Reaches General Availability with Automated Pull RequestsAWS Transform Continuous Modernization Reaches General Availability with Automated Pull RequestsAWS Transform Continuous Modernization Reaches General Availability with Automated Pull Requests

    AL
    Aria Lin

    August 4, 2026

    AWS Transform, the company's continuous modernization platform, reached general availability on August 3, 2026, with automated pull request generation across connected GitHub, GitLab, and Bitbucket repositories. The platform now monitors code at organization scale and

    AWS Transform Continuous Modernization Reaches General Availability with Automated Pull Requests

    AWS Transform, the company's continuous modernization platform, reached general availability on August 3, 2026, with automated pull request generation across connected GitHub, GitLab, and Bitbucket repositories. The platform now monitors code at organization scale and autonomously submits validated fixes for technical debt, security vulnerabilities, and framework upgrades. The real shift is architectural: this moves AWS from one-time migration tooling into permanent infrastructure for code quality, positioning the platform as both CI/CD complement and competitor to standalone static analysis vendors who detect issues but leave remediation to human teams.

    For enterprises managing hundreds of microservices across distributed development teams, the continuous monitoring model addresses the structural problem that technical debt accumulates faster than quarterly refactoring sprints can resolve it. AWS Transform runs analyses on customer-defined schedules, creates branches with validated code changes, and opens merge requests without human initiation.

    What's new

    AWS Transform continuous modernization moved from preview to general availability across all AWS Regions where the base Transform service operates. The platform connects to GitHub organizations, GitLab groups, and Bitbucket workspaces, scanning repositories on demand or on recurring schedules set by the customer.

    Analyses prioritize findings across five categories: technical debt, security vulnerabilities, agentic readiness (preparation for AI-assisted development workflows), modernization readiness, and custom analysis criteria defined by the engineering team. For findings with associated remediations, Transform creates a branch and opens a pull request or merge request containing validated code changes.

    Analysis and remediation run in the customer's AWS account using the customer's credentials. Source code remains under customer control and is not uploaded to AWS infrastructure. Teams can run analyses locally via the AWS Transform CLI or remotely using Amazon EC2 or AWS Batch compute resources.

    The platform integrates with AWS Security Agent to detect and remediate security vulnerabilities at source. Engineers access Transform through the web application, the Kiro Power IDE plugin, agent plugins, or the command-line interface. Repositories can be organized using labels, and the platform supports local repository analysis for teams with airgapped or on-premises source control systems.

    Wide shot of a modern GitHub repository merge request interface viewed from behind a developer's shoulder in an open-plan office at blue hour, hands hovering over keyboard, ambient cool teal light from large windows, shallow depth of field isolating the figure against softly blurred team workspace, shot on 35mm lens with natural twilight color grading.

    AWS announced the autonomous dependency, API, and framework upgrade capability at re:Invent 2025, expanding Transform's original focus from .NET application porting to continuous modernization across languages and frameworks. The continuous modernization capability entered preview in June 2026 before reaching general availability two months later.

    Why it matters

    United Airlines uses AWS AI systems to operate more than 5,000 daily flights, Audi uses the platform to connect over 50 manufacturing plants worldwide, and Siemens Mobility converted 175 years of historical operational data into searchable insights using AWS tools.

    These deployment scales illustrate the problem Transform addresses: enterprises managing multi-region production systems cannot schedule downtime for manual code remediation, and security vulnerabilities discovered in shared dependencies propagate across hundreds of microservices faster than security teams can patch them manually. The continuous monitoring model treats code quality and security debt as operational concerns requiring automated responses, not quarterly planning exercises.

    The 24/7 repository monitoring capability means new vulnerabilities trigger remediation workflows without waiting for the next scheduled security review. For organizations subject to compliance frameworks that mandate patching timelines (PCI-DSS requires critical vulnerabilities patched within 30 days, SOC 2 audits examine remediation velocity), automated pull request generation compresses the window between vulnerability disclosure and deployed fix.

    The agentic readiness analysis category signals AWS positioning Transform for AI-assisted development workflows where code generation tools produce higher volumes of code requiring systematic quality review. As GitHub Copilot, which moved from technical preview in June 2021 to general availability in June 2022 and added agent mode with GPT-4o, o1, o3-mini, Claude 3.5 Sonnet, and Gemini 2.0 Flash integration in February 2025, increases code output per developer, the bottleneck shifts from writing code to reviewing and maintaining it.

    Tight macro close-up of a developer's hands typing on a mechanical keyboard with a soft-focus row of glowing amber commit status LEDs on a custom hardware dashboard in the foreground, warm golden-hour sunlight streaming across the desk from a nearby window creating long shadows and highlights on keycaps.

    Air Canada, Experian, QAD, Teamfront, Thomson Reuters, and Verisk use AWS Transform in production environments. The customer base spans regulated industries (financial services, travel, data aggregation) where code audit trails and automated compliance reporting justify the operational overhead of integrating continuous analysis into existing CI/CD pipelines.

    Competitive Landscape

    AWS offers over 240 comprehensive services across cloud and AI infrastructure, positioning Transform as the code quality layer in a vertically integrated platform rather than a standalone developer tool. The integration with AWS Security Agent creates a closed-loop remediation path unavailable to third-party static analysis vendors who detect issues but rely on external ticketing systems to drive fixes.

    SonarQube, the open-core static code analysis platform that released Server 2025.1 in January 2025, scans for bugs, vulnerabilities, and code smells across multiple languages and integrates with GitHub, Bitbucket, Azure, and GitLab. SonarQube Advanced Security scans for vulnerabilities in third-party open-source dependencies for Java, C#, and JavaScript/TypeScript code, while AI Code Assurance applies separate rule sets to code created by GitHub Copilot. The platform's Secrets Detection flags passwords, API keys, and credentials in both repositories and supported IDEs. SonarQube Community Build offers a free and open-source version lacking proprietary features.

    The differentiation centers on remediation automation: SonarQube flags issues and integrates analysis into pull request workflows, but engineers write the fixes. Transform generates the validated code changes and opens merge requests autonomously. For enterprises with hundreds of repositories and distributed teams across time zones, the labor savings compound: one security vulnerability in a widely used internal library might require identical fixes across 40 microservices, a task Transform handles without human coordination.

    Independent analyst commentary specifically on this announcement was not publicly available at publication time.

    What's next

    AWS Transform continuous modernization is available now in all AWS Regions supporting the base Transform service. The company has not disclosed pricing structure, whether the service bills per repository, per analysis run, per remediation, or as a subscription tier within existing AWS support plans.

    Over-the-shoulder medium shot of a developer's hands hovering above a laptop keyboard in a bright, sunlit modern office with floor-to-ceiling windows, ready to approve an incoming merge request notification, soft morning light streaming across the desk, shallow depth of field, natural bright high-key lighting

    The custom analysis criteria capability allows teams to define organization-specific code standards beyond the five built-in categories, addressing the enterprise requirement for internal framework compliance, deprecated API detection, and proprietary security rules. This extensibility determines whether Transform replaces or complements existing static analysis toolchains: teams with mature SonarQube deployments encoding years of institutional knowledge face migration costs if custom rules cannot transfer.

    The Kiro Power IDE plugin and CLI availability mean developers can trigger analyses from their local environment without context-switching to the web application. For teams adopting Transform incrementally, the local analysis mode allows experimentation on individual repositories before connecting organization-wide source control integrations that require elevated permissions and security review.

    AWS has not published case studies quantifying remediation accuracy rates, false positive percentages, or the proportion of generated pull requests merged without human modification. These metrics determine operational trust: a 40% merge rate without edits justifies automation, while a 5% rate creates review overhead that negates labor savings.

    For a security architect managing compliance across 200 microservices, Transform's value proposition depends on one unpublished number: the percentage of automated remediations that pass security review without modification. If that figure exceeds 60%, the platform compresses mean time to remediation from weeks (human queue depth) to hours (automated PR generation plus review). Below 30%, it generates review backlog instead of resolving it, and the CISO's decision flips from enthusiastic adoption to pilot-only caution until accuracy improves.

    AWS built Transform for the problem that becomes visible only at scale: technical debt accumulates continuously, but remediation happens in batches, and the gap between detection and fix widens until a security incident forces emergency response. The shift from migration tool to permanent quality infrastructure means AWS is betting that code maintenance becomes an always-on operational concern, not a project phase. Whether that bet pays off depends on whether engineering teams trust the automated pull requests enough to merge them faster than they could write the fixes themselves.

    -- Aria Lin, Enterprise Technology Analyst

    Sources: AWS · AWS Transform General Availability Announcement · AWS Transform Continuous Modernization Documentation

    More on Revuzia