Translating an AWS EKS Stack to Azure AKS: The Architectural Decisions Behind a Real Migration
Migrating a production EKS stack to AKS is not a service-by-service translation exercise. It is a sequence of architectural decisions that the AWS-to-Azure mapping tables on Microsoft Learn quietly skip over. This post is about the decisions that shaped a real five-week migration of four production apps from eu-west-2 to West Europe, and what I would do differently.
There is a comforting table on Microsoft Learn that maps AWS services to Azure services. RDS to Flexible Server. Cognito to Entra ID B2C. SQS to Service Bus. ECR to ACR. S3+CloudFront to Blob+Front Door. The table is correct. It is also misleading, because it implies the migration is a translation problem.
