Agentic readiness and modernization analysis are now available in AWS Transform continuous modernization

Earlier this year we introduced Agentic Readiness as a method for evaluating whether applications can safely support AI agent interaction, and then shipped Agentic Readiness Analysis (ARA) and Modernization Analysis (MODA) as managed transformation definitions in AWS Transform. Those analyses gave you per-repository and portfolio-level assessments you could run on demand via the ATX CLI.

With the launch of AWS Transform continuous modernization (preview), ARA and MODA are first-class analysis types you can run continuously across your entire connected portfolio, with findings tracked, trended, and remediated alongside your other technical debt.

What’s new

Running ARA and MODA inside continuous modernization gives you capabilities that standalone CLI execution does not:

Continuous scheduling. Configure ARA and MODA to run on a recurring cadence (daily, weekly, or custom cron). Every time your code changes, your readiness posture is re-evaluated automatically.

Drift detection. When a repository that was previously classified as Agent-Ready or Cloud-Native Ready introduces a regression (removed API documentation, hardcoded credentials, deprecated dependencies), continuous analysis flags it immediately rather than waiting for the next manual review.

Centralized findings management. ARA and MODA findings flow into the same prioritized list as tech debt and security findings. You triage, dismiss, and track resolution from a single view across all analysis types.

Autonomous remediation. For findings that have an associated fix transform, continuous modernization can generate pull requests automatically. Teams review and merge on their own schedule; re-analysis marks resolved findings as obsolete without manual confirmation.

Portfolio-level trending. Track your organization’s agentic readiness and modernization maturity over time. See which teams are closing gaps and where systemic patterns are emerging.

Continuous modernization dashboard showing ARA and MODA findings alongside tech debt and security findings across connected repositories

How to run ARA and MODA in continuous modernization

From the AWS Transform web console

1. Connect your source code repositories (GitHub, GitLab, Bitbucket, or local directories).
2. Navigate to Analyses and select agentic-readiness or modernization-readiness as the analysis type.
3. Choose target repositories (individually, by label, or select all).
4. Run on demand or configure a recurring schedule.

Analysis configuration screen showing agentic-readiness selected as analysis type with repository targeting options

From the ATX CLI

# Start the continuous modernization server (the Kiro Power can start this for you)

atx ct server &

# Connect a source (github | gitlab | bitbucket | local)

atx ct source add --name my-portfolio --provider github \

  --org my-org --token $GIT_TOKEN

# Discover the repositories in the connected source

atx ct discovery scan --source my-portfolio

# Run Agentic Readiness Analysis on one repository

atx ct analysis run --type agentic-readiness \

  --repo my-portfolio::my-service --wait

# Run Modernization Analysis across the whole source (omit --repo for all repos)

atx ct analysis run --type modernization-readiness \

  --source my-portfolio --wait

# Review findings (filter to narrow the result set) and trigger remediation

atx ct findings list --source my-portfolio --min-severity high --json

atx ct remediation create --ids <id1>,<id2> --name "ARA remediation"

From the Kiro Power or agent plugin

Ask the agent directly: “Run an agentic readiness analysis on my connected repositories” or “Set up a weekly modernization analysis for my portfolio.” The agent handles source configuration, execution, and scheduling.

Via MCP

Continuous modernization ships an MCP server so you can drive ARA and MODA from any MCP-compatible coding agent. Start it over stdio or HTTP:

# stdio transport (default)

atx ct mcp

# HTTP transport

atx ct mcp --transport http --port 3100

The server exposes the full continuous modernization surface as agent tools — including analysis/run, findings/list, remediation/create, discovery/scan, and schedule/create — so an agent can connect a source, run an agentic-readiness or modernization-readiness analysis, retrieve findings, open remediations, and set up recurring schedules without leaving its own workflow. You can also pair the MCP server with the Kiro Power: the Power orchestrates the higher-level workflow while the MCP tools execute the underlying operations. The orchestrator we use is open source — see the Agentic Readiness Analysis Orchestrator sample on GitHub.

A coding agent driving ARA and MODA through the continuous modernization MCP server.

Analysis output

Both ARA and MODA produce a four-artifact report bundle per repository:

Within continuous modernization, individual findings are also surfaced in the centralized findings view with severity (High, Medium, Low), status tracking, and links to the relevant source files.

Detailed findings view showing individual ARA findings with severity, file-level evidence, and remediation recommendations

Availability and pricing

AWS Transform continuous modernization (preview) is available in US East (N. Virginia) and Europe (Frankfurt). ARA and MODA are included as managed analysis types at no additional charge beyond standard AWS Transform pricing (per agent minute; a typical 12K-line service analysis costs $1 to $2).

To get started, visit the AWS Transform web application, install the Kiro Power, or connect via MCP from your existing coding agent.

Learn more

• AWS Transform continuous modernization announcement
• Proactively reduce tech debt autonomously with AWS Transform continuous modernization
• Agentic Readiness: A Method for Evaluating Applications for Agent Interaction
• New in AWS Transform: Analyze Your Code for Modernization and Agentic Readiness
• AWS Transform continuous modernization user guide