Skip to content
ittechwire

Technology news, clearly sourced

  1. Home
  2. Cloud

Cloud

AWS Transform can now convert Azure SDK code in .NET apps to AWS SDK code

AWS says its .NET modernization agent now rewrites calls to selected Azure services for their AWS counterparts, covering application code but not infrastructure.

ittechwire Editorial3 min readSources: 2
Aerial view of an Amazon Web Services data center campus near Umatilla, Oregon, with long white-roofed buildings and an electrical substation.
Tedder · CC BY-SA 4.0

Key points

  1. 1AWS made Azure SDK to AWS SDK code conversion generally available in AWS Transform, announced on Oct. 16.
  2. 2Supported paths per AWS: Azure Functions to Lambda, Blob Storage to S3, Queue Storage to SQS; Cosmos DB to DynamoDB is in preview.
  3. 3The feature converts application code only and does not migrate cloud infrastructure, according to the user guide.
  4. 4Conversion options appear in the assessment report and modernization plan and can be customized or opted out of.
  5. 5Unconvertible code is flagged in TODO comments, stubbed code or a generated Next Steps file, AWS says.

Full story

AWS has made code conversion from the Azure SDK to the AWS SDK generally available in AWS Transform, according to an announcement posted on Oct. 16. The company presents the capability as a quicker way to move cloud-native .NET applications built for Microsoft Azure onto AWS. According to AWS, the .NET modernization agent in AWS Transform locates code that calls Azure services and rewrites it to use the corresponding AWS services.

AWS lists four supported conversions: Azure Functions are rewritten as AWS Lambda functions, Azure Blob Storage code is moved to Amazon S3, and Azure Queue Storage code is moved to Amazon SQS, while converting Azure Cosmos DB code to Amazon DynamoDB is offered as a preview. The user guide states that only these listed services are converted and suggests AWS Transform custom or an AI code companion such as Kiro for other services. AWS also notes that the feature handles application code only and does not migrate cloud infrastructure.

According to AWS, the service detects the Azure SDK in submitted source code and lays out conversion options in its assessment report and modernization plan, which users can accept or adjust before the modernization runs. AWS says it then checks that the changes are incorporated into the transformed code. The documentation describes conversion as automatic for eligible modern .NET applications, with behavior adjustable through agent chat, edits to the plan or a steering document, for example to skip some or all conversions, set naming conventions, change comment verbosity or point Blob Storage code at DynamoDB instead of S3.

Code that has no equivalent on AWS is flagged rather than converted: the user guide says it is marked with TODO comments, left as stubbed code or recorded in a Next Steps markdown file produced by AWS Transform. AWS says AWS Transform is offered in eight AWS Regions, namely Frankfurt and London in Europe, Mumbai, Tokyo, Seoul and Sydney in Asia Pacific, as well as Canada (Central) and US East (N. Virginia).

Why it matters

Rewriting service-specific SDK calls is a significant part of the work of moving .NET applications off Microsoft Azure. AWS is automating part of that work for a small set of services, though teams still have to migrate infrastructure separately and handle any code the tool flags as unconverted.

Timeline

  1. · Published

Topics#AWS Transform#Microsoft Azure#.NET#cloud migration#AWS Lambda#code modernization

Sources

This story draws on the following sources. Read them for full context.

  1. 1Amazon Web Services · Official statementAWS Transform announces Azure-to-AWS cloud-native code conversionaws.amazon.com
  2. 2Amazon Web Services · Primary sourceConvert cloud-native code to AWS services - AWS Transform User Guidedocs.aws.amazon.com