Self-managed nodes
A cluster contains one or more Amazon EC2 nodes that pods are scheduled on. Amazon EKS nodes run in your Amazon account and connect to the control plane of your cluster through the cluster API server endpoint. You deploy one or more nodes into a node group. A node group is one or more Amazon EC2 instances that are deployed in an Amazon EC2 Auto Scaling group.
All instances in a node group must have the following characteristics:
-
Be the same instance type
-
Be running the same Amazon Machine Image (AMI)
-
Use the same Amazon EKS node IAM role
Note You can't use the same role that is used to create any clusters.
A cluster can contain several node groups. If each node group meets the previous requirements, the cluster can contain node groups that contain different instance types and host operating systems. Each node group can contain several nodes.
Amazon EKS nodes are standard Amazon EC2 instances. You're billed for them based on EC2 prices. For
more information, see Amazon EC2
pricing
Amazon EKS provides specialized Amazon Machine Images (AMI) that are called Amazon EKS optimized
AMIs. The AMIs are configured to work with Amazon EKS and include Docker,
kubelet
, and the Amazon IAM Authenticator. The AMIs also contain a specialized
bootstrap script
If you restrict access to the public endpoint of your cluster using CIDR blocks, we recommend that you also enable private endpoint access. This is so that nodes can communicate with the cluster. Without the private endpoint enabled, the CIDR blocks that you specify for public access must include the egress sources from your VPC. For more information, see Amazon EKS cluster endpoint access control.
To add self-managed nodes to your Amazon EKS cluster, see the topics that follow. If you launch self-managed nodes manually, add the following tag to each node. For more information, see Adding and deleting tags on an individual resource. If you follow the steps in the guides that follow, the required tag is automatically added to nodes for you.
Key | Value |
---|---|
|
|
For more information about nodes from a general Kubernetes perspective, see Nodes
Topics