Convert Azure cloud-native .NET code to AWS with AWS Transform
AWS Transform for .NET can convert Azure cloud-native code, such as Azure SDK calls, to equivalent AWS services. The AWS blog walks through moving an Azure Functions queue-triggered function to AWS Lambda with SQS and DynamoDB, then customizes a larger transformation that redirects Cosmos DB to Amazon S3. It is a useful reference for .NET teams planning a cross-cloud migration.
Key points
- Supported Azure conversions run from Visual Studio, the web console, the CLI, the Kiro power or MCP.
- An Azure Functions queue trigger is rewritten as an AWS Lambda function triggered by SQS.
- The Cosmos DB to DynamoDB conversion is still in preview.
- Unsupported Azure services get a best-effort conversion that needs manual review.
- The modernization plan can be edited to redirect Cosmos DB to S3 or move Key Vault to Secrets Manager.
Moving a .NET application from Azure to AWS often leaves Azure SDK calls in the code. AWS Transform for .NET can rewrite supported Azure services into their AWS equivalents, and the Cosmos DB to DynamoDB path is still in preview. For services outside the supported list, the agent makes a best-effort conversion that needs careful review.
The post runs two examples. In the first, an Azure Functions function triggered by an Azure Queue is converted to AWS Lambda, Amazon SQS and DynamoDB using the default plan from Visual Studio. In the second, an open-source news app is customized: Cosmos DB is redirected to Amazon S3 to consolidate storage, and Azure Key Vault and timer triggers are moved to Secrets Manager and EventBridge. The useful takeaway is how the plan can be edited before the agent makes changes, which matters for teams with mixed Azure dependencies.
Real-world use
- Moving an Azure Functions help desk service that reads from an Azure Queue to AWS Lambda and SQS.
- Consolidating a .NET app's Cosmos DB and Blob Storage usage onto Amazon S3.
- Migrating a background job that relies on Key Vault and timer triggers to Secrets Manager and EventBridge.
Why it matters
If your .NET service still calls Azure SDKs, the agent can produce a first AWS version to review instead of rewriting everything by hand. You still need to verify retry, idempotency and credential behavior after the conversion.
Related stories
- Azure SDK October 2026: Azure Core, managed identity and Cosmos DB for Rust 1.0.0Azure SDK Blog5 d ago
- Building enterprise apps with SharePoint Embedded: limits, throttling and permissionsMicrosoft 365 Developer BlogOct 22
- A secure enterprise chat with React, .NET 10 and Microsoft FoundryDEV Community: #dotnet1 d ago