AKS for Amazon EKS professionals
This series of articles helps professionals who are familiar with Amazon Elastic Kubernetes Service (Amazon EKS) to understand Azure Kubernetes Service (AKS). The series highlights key similarities and differences between these two managed Kubernetes solutions.
The series articles compare AKS with Amazon EKS for 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
These articles provide recommended architectures and practices to improve AKS deployment security, compliance, management, and observability. For basic AKS implementation, see Baseline architecture for an Azure Kubernetes Service (AKS) cluster and AKS landing zone accelerator.
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 Choose an Azure compute service and Compare Container Apps with other Azure container options.
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
- Compare storage on Azure and AWS
Contributors
This article is maintained by Microsoft. It was originally written by the following contributors.
Principal authors:
- Laura Nicolas | Senior Software Engineer
- Paolo Salvatori | Principal Service Engineer
Other contributors:
- Chad Kittel | Principal Software Engineer
- Ed Price | Senior Content Program Manager
- Theano Petersen | Technical Writer
To see non-public LinkedIn profiles, sign in to LinkedIn.
Next steps
- Kubernetes identity and access management
- Kubernetes monitoring and logging
- Secure network access to Kubernetes
- Storage options for a Kubernetes cluster
- Cost management for Kubernetes
- Kubernetes node and node pool management
- Cluster governance
Related resources
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for