Understanding the EKS architecture
Every EKS cluster will have a single endpoint URL used by tools such as kubectl, the main Kubernetes client. This URL hides all the control plane servers deployed on an AWS-managed VPC across multiple Availability Zones in the region you have selected to deploy the cluster to, and the servers that make up the control plane are not accessible to the cluster users or administrators.
The data plane is typically composed of EC2 workers that are deployed across multiple Availability Zones and have the kubelet and kube-proxy agents configured to point to the cluster endpoint. The following diagram illustrates the standard EKS architecture:
Figure 2.1 – High-level overview of EKS architecture
The next sections will look into how AWS configures and secures the EKS control plane along with specific commands you can use to interact with it.
Understanding the EKS control plane
When a new cluster is created, a new...