What changed
AWS has introduced a multi-stage transformation methodology using Amazon Bedrock, Kiro IDE, and AWS Transform to modernize legacy mainframe Assembler applications into Java Spring Boot services on AWS. This approach involves converting Assembler to COBOL as an intermediate step before Java transformation, reducing risk and preserving business logic.
What this means in practice
The solution enables organizations to systematically extract business rules from Assembler code, convert them through an intermediate COBOL stage, and deploy modernized applications as Java Spring Boot services on AWS. This process includes AI-assisted code analysis, validation checkpoints, and functional equivalence testing to ensure business rules remain intact throughout the modernization journey. The methodology is designed for environments where Assembler programs execute batch processes connected with COBOL, interact with databases, and process files, running on IBM z/OS mainframe infrastructure.
Limitations and availability
The transformation workflow requires an active AWS account with specific IAM permissions for Amazon Bedrock, AWS Transform, and Amazon S3. Access to Amazon Q Developer or Kiro for AI-assisted code analysis, AWS Transform for COBOL to Java conversion, and an Amazon S3 bucket configured for source code and artifact storage are also prerequisites. The solution is available for organizations with Assembler code inventory, business and technical subject matter experts, and test data sets with expected outputs for functional equivalence testing. The supplied announcement does not specify exact performance benchmarks or availability timelines for the solution.
