Overview There are three tasks to perform when building a cluster: AWS shared responsibility model AWS operates, manages, and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the services operate. This means that AWS is responsible for protecting the global infrastructure that runs all the services offered in the AWS Cloud, including AWS Regions, Availability Zones, and edge locations. The AWS global infrastructure includes the facilities, network, hardware, and operational software [for example, host operating system (OS) and virtualization software] that support the provisioning and use of

Why have Amazon EKS manage your data plane? Managing a complex infrastructure of many worker nodes and worrying about automatic scaling and updates is challenging. Additionally, you may have many different teams provisioning nodes in a cluster, and they might all be doing it differently. These differences make standardization difficult. By allowing Amazon EKS to manage some or all of your data plane, you can simplify your infrastructure and maintain standardization. Select each of the following three tabs to learn about each category. Using Fargate To use Fargate with Amazon EKS, you must create Fargate profiles. Fargate profiles specify which

Amazon EKS manages the Kubernetes control plane In a standard Kubernetes deployment, you are responsible for designing, implementing, and maintaining all components of the control plane and the worker nodes.  Amazon EKS provides a scalable, highly available control plane. Amazon EKS automatically manages the availability and scalability of the Kubernetes API servers and the etcd persistence layer for each cluster. This gives you more time to focus on running your application workloads in Kubernetes. Amazon EKS availability and API The Amazon EKS control plane consists of at least two API server nodes and three etcd nodes across three Availability Zones.