eksctl CLI
The official Amazon EKS CLI creates and manages Kubernetes clusters from configuration that an agent can prepare for review.
- 5,218 ★ on the repository
- Last commit
Broad access
Why this level
- The CLI provisions and changes billable AWS resources, network settings and related IAM permissions under the account.
Install
Manual install
# for ARM systems, set ARCH to: `arm64`, `armv6` or `armv7`
ARCH=$(uname -m | sed 's/x86_64/amd64/' | sed 's/aarch64/arm64/')
PLATFORM=$(uname -s)_$ARCH
curl -sLO "https://github.com/eksctl-io/eksctl/releases/latest/download/eksctl_$PLATFORM.tar.gz"
# (Optional) Verify checksum
curl -sL "https://github.com/eksctl-io/eksctl/releases/latest/download/eksctl_checksums.txt" | grep $PLATFORM | sha256sum --check
tar -xzf eksctl_$PLATFORM.tar.gz -C /tmp && rm eksctl_$PLATFORM.tar.gz
sudo install -m 0755 /tmp/eksctl /usr/local/bin && rm /tmp/eksctlFirst complete Unix README block with architecture detection, download and installation. Its checksum step uses sha256sum; macOS needs a suitable utility.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The CLI provisions and changes billable AWS resources, network settings and related IAM permissions under the account.
This is third-party code. Review the repository files before installing.
What it does
eksctl manages Amazon EKS clusters through AWS CloudFormation. An agent can prepare cluster parameters, node groups and related settings for review before an approved terminal operation. Configuration files make region and resource choices explicit. The CLI supports cluster lifecycle work, EKS Auto Mode and hybrid nodes. Cluster creation adds connection data to local kubeconfig, and subsequent Kubernetes commands use the selected AWS identity and its access.
Who it is for. Amazon EKS administrators preparing cluster and node-group configuration with an agent before provisioning AWS resources.
Good fit when
- A team approved a new EKS cluster and wants its parameters recorded.
- An agent prepares node-group configuration for a workload.
- For a supported project, the team needs EKS Auto Mode.
- Cluster creation should provide local Kubernetes connection configuration.
Not a fit when
- The Kubernetes environment is outside Amazon EKS.
- AWS provisioning and its costs have not been approved.
- The identity lacks the required CloudFormation, EKS and IAM permissions.
Example request
Prepare a test EKS cluster configuration in the approved region and list required resources and permissions without creating it yet.Limitations
Configured AWS credentials and a Kubernetes token helper must be available to the CLI. Cluster creation needs permissions across services including CloudFormation, EKS and IAM; Kubernetes access alone is insufficient. With default settings, eksctl provisions cloud nodes and a dedicated network, so inspect region, sizing and quotas beforehand. Auto Mode and Hybrid Nodes require eksctl 0.195.0 or newer; verify the installed version before selecting those modes.
How to disable. Stop eksctl jobs and inspect CloudFormation stack state. Removing the CLI does not delete the cluster or end AWS charges.
FAQ
What creates the resources?
AWS CloudFormation; inspect the associated stacks for creation state.
What changes locally after cluster creation?
Cluster connection details are added to kubeconfig.
Does kubectl need a token helper?
Yes, for example `aws eks get-token`, using the appropriate AWS identity.
Does uninstalling the tool stop cluster charges?
No. Provisioned AWS resources remain until separately deleted.
Where is the recommended binary?
In official eksctl GitHub Releases; AWS does not support third-party installers.
Discussion
No questions or reviews yet.
Related
CLI toolsThe Kubernetes configuration manager merges connections and switches contexts so agents use the intended cluster.
The Kubernetes terminal interface shows resources and logs so users can inspect cluster state alongside agent work.
The CLI adds tags and labels to Terraform and OpenTofu files for consistent agent-prepared AWS, GCP and Azure configuration.
Black-box auditor runs a released CLI, catches side writes to disk and gives agents a command index with a readiness score.
A CLI that scaffolds an application from selected stack parts and helps add capabilities to an existing generated project.
A CLI that gives six coding agents project context, over 80 skills, verification and resumable tasks across sessions
README in short
The README separates Unix, Windows and container routes. Minimum IAM policies are documented separately.