Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This series of articles helps professionals who are familiar with Amazon Elastic Kubernetes Service (EKS) understand Azure Kubernetes Service (AKS). The series highlights key similarities and differences between these two managed Kubernetes solutions.
The articles compare AKS with Amazon EKS in the following Kubernetes design areas:
- Identity and access management
- Cluster logging and monitoring
- Secure network topologies
- Storage options
- Cost optimization and management
- Agent node and node pool management
- Cluster governance
- Workload migration
These articles provide recommended architectures and practices to improve AKS deployment security, compliance, management, and observability. Specifically, the Migrate EKS to AKS article provides strategies to migrate typical stateless and stateful workloads. For basic AKS implementation, see Baseline architecture for an AKS cluster and AKS in an application landing zone.
AKS isn't the only way to run containers in Azure, and Amazon EKS is only one of the container options for Amazon Web Services (AWS). These articles don't compare Azure services like Azure Container Apps, Azure Container Instances, and Azure App Service with AWS services like Amazon Elastic Container Service or AWS Fargate.
For more information about other Azure services that can host containerized workloads, see the following articles:
- Choose an Azure compute service
- Choose an Azure container service
- Compare Container Apps with other Azure container options
- General architectural considerations to choose an Azure container service
The following articles compare Azure and AWS core platform components and capabilities:
- Azure and AWS accounts and subscriptions
- Compute services on Azure and AWS
- Relational database technologies on Azure and AWS
- Messaging services on Azure and AWS
- Networking on Azure and AWS
- Regions and zones on Azure and AWS
- Resource management on Azure and AWS
- Multicloud security and identity with Azure and AWS
- Storage on Azure and AWS
Contributors
Microsoft maintains this article. The following contributors wrote this article.
Principal authors:
- Paolo Salvatori | Principal Service Engineer
- Laura Nicolas | Senior Cloud Solution Architect
Other contributors:
- Chad Kittel | Principal Software Engineer
- Ed Price | Senior Content Program Manager
- Theano Petersen | Technical Writer
To see nonpublic LinkedIn profiles, sign in to LinkedIn.
Next steps
- Baseline architecture for an AKS cluster
- Cloud Adoption Framework guidance for adopting AKS in Azure landing zones