# AWS Transform

AWS Transform is an agentic AI service for assessing, migrating, and modernizing enterprise infrastructure, applications, and source code.

Cloud service · AWS. Updated 2026-11-15. Page: https://blowstack.com/tools/cloud-services-hub/aws-transform

> AWS Transform provides collaborative workflows for server migrations, mainframe modernization, Windows and .NET modernization, and repeatable code transformations. Engineers use it to analyze dependencies, plan migration waves, generate modernization artifacts, and execute supported transformations with human review and approval.

Practice exams covering AWS Transform: [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 9 key features of AWS Transform

1. **Collaborative transformation workspaces**: Manage job plans, artifacts, approvals, and execution history in a shared workspace. Engineers can refine plans conversationally and repeat tasks when requirements or source inputs change.
2. **Discovery, assessment, and wave planning**: Analyze infrastructure inventories, identify application dependencies, and organize servers into migration waves. Assessment capabilities also cover supported storage workloads and on-premises Apache Kafka migration to Amazon MSK.
3. **Landing zone and network preparation**: Create or extend supported landing zones and generate target AWS network configurations. Teams can build new networks, translate existing networks, or modernize access rules into security groups for existing VPCs.
4. **Guided server rehosting**: Move supported virtual and bare metal servers to Amazon EC2 through replication, test launches, and cutover workflows. Validate application dependencies and target connectivity before scheduling production cutover.
5. **.NET and Windows modernization**: Transform supported .NET Framework applications into Linux-ready, cross-platform .NET and optionally generate unit tests. Supported workflows also include Azure-to-AWS SDK conversion and SQL Server schema conversion for Aurora PostgreSQL.
6. **Mainframe analysis and modernization**: Analyze and modernize supported IBM z/OS and Fujitsu GS21 workloads. Supported z/OS reimagine workflows provide field-level business-function discovery and requirements coverage reporting to support design review.
7. **Custom code transformations**: Define repeatable code changes using natural-language instructions, documentation, and examples, or select AWS-managed transformations. Apply the same transformation across multiple codebases rather than implementing each change independently.
8. **Continuous technical debt remediation**: Scan repositories for outdated dependencies, security vulnerabilities, and code quality issues. Supported remediation workflows create branches and pull or merge requests in GitHub, GitLab, and Bitbucket for engineering review.
9. **Source code containerization**: Containerize supported applications from source code and deploy them to Amazon ECS or Amazon EKS. Review container configuration, external dependencies, and runtime requirements before promoting the resulting deployment.

## Where AWS Transform is used

1. **Data center exit**: Discover virtual and physical servers, group dependent applications, prepare AWS networking, and migrate servers to EC2 in controlled waves. Include test launches and rollback criteria in each wave's acceptance plan.
2. **Windows application modernization**: Modernize supported .NET Framework applications for cross-platform .NET and evaluate Linux deployment. Identify native Windows dependencies early and validate generated changes with application regression tests.
3. **Mainframe application redesign**: Analyze legacy applications, identify business functions, and review requirements coverage before implementing a modernized design. Use generated documentation and dependency information to scope incremental changes.
4. **Portfolio-wide code maintenance**: Apply common framework upgrades or organization-specific code changes across repositories. Combine recurring analysis with generated remediation pull requests while retaining normal code review and CI checks.
5. **Migration business case development**: Assess supported infrastructure, storage, and Kafka workloads to compare target AWS options and estimated costs. Review sizing assumptions and service compatibility before using the assessment to establish a migration budget.
6. **Azure application migration**: Convert supported Azure SDK usage in .NET applications to equivalent AWS service integrations. For example, assess a function using Azure Cosmos DB for conversion to AWS Lambda and Amazon DynamoDB, then validate data access semantics and operational behavior.

## How AWS Transform is priced

- **No additional AWS Transform service charge**: AWS Transform is available without an additional service charge. Service quotas and workload-specific limits still apply; a quota allowance is not a guarantee of unlimited processing capacity.
- **Underlying AWS resource charges**: Resources used during migration, testing, and production are billed under their respective service pricing. Budget for items such as EC2 instances, storage, databases, container infrastructure, and applicable data transfer, and remove temporary test resources when they are no longer needed.

## Services AWS Transform works with

A common migration architecture separates the transformation workspace from the target application environment. AWS Transform analyzes inventories and network inputs, prepares or extends a landing zone, and guides server migration to Amazon EC2. Amazon VPC provides the target networking and security boundaries. Review generated connectivity rules against actual application dependencies before testing, and keep production cutover behind explicit acceptance criteria.

Application modernization uses different target services according to the workload. Source code containerization can deploy supported applications to Amazon ECS or Amazon EKS. Full-stack Windows modernization can convert SQL Server DDL for Aurora PostgreSQL, but schema conversion should be paired with a separate plan for data movement, database validation, and connection changes. These target resources incur their own service charges.

For ongoing maintenance, continuous modernization connects repository analysis with remediation branches and pull requests. Recurring analysis can run on managed infrastructure or on a provisioned EC2 or AWS Batch stack scheduled through Amazon EventBridge Scheduler. Preserve CI checks, security scanning, and reviewer approval so automated transformations enter production through the same controls as manually authored changes.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: AWS Transform server migration workflows rehost supported source servers onto Amazon EC2. For example, migrate an application wave into a test environment, verify service connectivity and instance sizing, and then approve production cutover.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Network workflows generate and deploy target VPC architectures or convert source access rules into security groups for existing VPCs. For example, translate a source application's connection rules, then inspect the resulting ports and permitted sources before deployment.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: AWS Transform can assess and extend supported existing AWS Control Tower landing zones rather than requiring an entirely new foundation. For example, run a foundation gap analysis before adding the accounts and controls needed for a migration program.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: Full-stack Windows modernization supports SQL Server DDL conversion and deployment of the resulting Aurora PostgreSQL database in supported Regions. For example, select the target Region in the transformation plan and validate the converted schema before separately planning data migration and application cutover.

## What is AWS Transform

AWS Transform helps engineering teams assess and execute changes to infrastructure, applications, and code. Its specialized agents support migration planning, server rehosting, network conversion, mainframe modernization, .NET modernization, and custom code transformations. A shared workspace brings together job plans, conversations, artifacts, approvals, and execution history so that infrastructure engineers, application developers, and reviewers can work on the same transformation.

A typical project begins with source material such as server inventories, application repositories, network configurations, or mainframe code. Engineers describe the desired outcome through a conversational interface and refine the resulting job plan. Tasks can be revisited when assumptions change. Treat generated plans and artifacts as engineering inputs: validate discovery completeness, dependency relationships, security requirements, and operational constraints before approving deployment or cutover.

For infrastructure migration, AWS Transform supports discovery, application grouping, dependency analysis, migration wave planning, landing zone creation, network migration, and server rehosting to Amazon EC2. Supported source environments include VMware, Hyper-V, and other virtual or bare metal server environments. Network workflows can translate existing configurations, build a new network, or convert access rules into security groups for existing VPCs. Landing zone workflows can assess and extend supported existing AWS environments, including AWS Control Tower deployments, and offer an infrastructure-as-code-only mode.

Application modernization includes moving supported .NET Framework applications toward Linux-ready, cross-platform .NET. Available capabilities include generating unit tests for transformed code and converting supported Azure SDK usage to AWS SDK usage. Compatibility assessment remains important: unsupported native Win32 dependencies may require manual replacement, and repositories must contain supported .NET solutions. Generated tests provide additional coverage but do not replace regression testing against existing application behavior.

Mainframe workflows support assessment and modernization of IBM z/OS and Fujitsu GS21 workloads. For supported z/OS COBOL and PL/I reimagine workflows, business-function discovery can distinguish access at the data-field level, and requirements coverage reports help teams inspect traceability before implementation. Custom transformations let teams define organization-specific changes using natural language, documentation, and code samples. Continuous modernization can scan repositories, identify technical debt, and generate remediation pull requests for review.

Before starting a production program, confirm supported Regions, workload-specific limitations, and service quotas. Some mainframe data processing can occur outside the selected Region, so review cross-Region processing requirements before uploading regulated code or data. Plan separately for target infrastructure, replication, testing, rollback, and application acceptance. AWS Transform does not eliminate the need to verify functional equivalence, database correctness, performance, or security controls in the resulting environment.
