Built-in node pools
EKS Auto Mode ships with two built-in node pool configurations that cover the most common workload patterns:
Specify one or both node pools in
compute_config.node_pools:
Basic example
Custom node pools only
If you want to define your own Karpenter-style node pools without using the built-in EKS Auto Mode pools, setcreate_auto_mode_iam_resources = true and omit node_pools:
create_auto_mode_iam_resources is useful when you are managing your own node pools and need the EKS Auto Mode node IAM role and associated policy attachments without relying on built-in node pools.
IAM resources
When EKS Auto Mode is enabled, the module creates the following IAM resources by default:- An IAM role (
aws_iam_role.eks_auto) with theAmazonEKSAutoNodePolicyandAmazonEC2ContainerRegistryPullOnlypolicies attached - Policy attachments for any additional policies supplied via
node_iam_role_additional_policies - Optional permissions for custom tags on resources created by EKS Auto Mode (enabled by
enable_auto_mode_custom_tags, defaulttrue)
Disabling EKS Auto Mode
compute_config variable reference
The compute_config variable accepts the following attributes:
EKS Auto Mode with Hybrid Nodes
EKS Auto Mode can coexist with EKS Hybrid Nodes. A common configuration enables thesystem node pool for core EKS components while hybrid nodes handle on-premises workloads:
