platform-eks

To migrate EKS IAM roles for service accounts to AKS, you map IRSA to Azure Workload Identity. This translation rule allows your Kubernetes workloads to securely access cloud resources using managed identities instead of AWS-specific IAM integrations.

The best way to translate AWS EBS storage to Azure Disk is by mapping the EBS CSI driver to its Azure Disk equivalent. This ensures your persistent volume claims are correctly aligned with Azure's native storage infrastructure during the migration process.

To migrate the ALB Ingress Controller from EKS to AKS, you map it to the Azure Application Gateway Ingress Controller (AGIC). This translation supports safe, reviewable output by aligning your AWS ingress routing with Azure's native application gateway.

Yes, you can use this cross-cloud migration guidance for production container registries by mapping Amazon ECR to Azure Container Registry (ACR). This ensures your container images are correctly referenced and securely stored within the Azure environment.

Yes, EKS to AKS migration requires mapping observability configurations to maintain visibility into your workloads. The skill provides specific alignment guidance for translating AWS-native observability constructs to their Azure equivalents during cluster modernization.

When modernizing clusters to AKS, the EKS constructs that need translation include identity, storage, networking, container registry, and observability. Mapping these AWS-native constructs to Azure equivalents reduces manual effort and migration risk.