**Help improve this page**
To contribute to this user guide, choose the **Edit this page on GitHub** link that is located in the right pane of every page.
# Set up to use Amazon EKS
To prepare for the command-line management of your Amazon EKS clusters, you need to install several tools. Use the following to set up credentials, create and modify clusters, and work with clusters once they are running:
+ [Set up AWS CLI](install-awscli.md) – Get the AWS CLI to set up and manage the services you need to work with Amazon EKS clusters. In particular, you need AWS CLI to configure credentials, but you also need it with other AWS services.
+ [Set up kubectl and eksctl](install-kubectl.md) – The `eksctl` CLI interacts with AWS to create, modify, and delete Amazon EKS clusters. Once a cluster is up, use the open source `kubectl` command to manage Kubernetes objects within your Amazon EKS clusters.
+ Set up a development environment (optional)– Consider adding the following tools:
+ **Local deployment tool** – If you’re new to Kubernetes, consider installing a local deployment tool like [minikube](https://minikube.sigs.k8s.io/docs/) or [kind](https://kind.sigs.k8s.io/). These tools allow you to have an Amazon EKS cluster on your local machine for testing applications.
+ **Package manager** – [helm](helm.md) is a popular package manager for Kubernetes that simplifies the installation and management of complex packages. With [Helm](helm.md), it’s easier to install and manage packages like the AWS Load Balancer Controller on your Amazon EKS cluster.
## Next steps
+ [Set up AWS CLI](install-awscli.md)
+ [Set up kubectl and eksctl](install-kubectl.md)
+ [Quickstart: Deploy a web app and store data](quickstart.md)
# Set up AWS CLI
The [AWS CLI](https://aws.amazon.com/cli/) is a command line tool for working with AWS services, including Amazon EKS. It is also used to authenticate IAM users or roles for access to the Amazon EKS cluster and other AWS resources from your local machine. To provision resources in AWS from the command line, you need to obtain an AWS access key ID and secret key to use in the command line. Then you need to configure these credentials in the AWS CLI. If you haven’t already installed the AWS CLI, see [Install or update the latest version of the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) in the * AWS Command Line Interface User Guide*.
## To create an access key
1. Sign into the [AWS Management Console](https://console.aws.amazon.com/).
1. For single-user or multiple-user accounts:
+ **Single-user account –**:: In the top right, choose your AWS user name to open the navigation menu. For example, choose ** `webadmin` **.
+ **Multiple-user account –**:: Choose IAM from the list of services. From the IAM Dashboard, select **Users**, and choose the name of the user.
1. Choose **Security credentials**.
1. Under **Access keys**, choose **Create access key**.
1. Choose **Command Line Interface (CLI)**, then choose **Next**.
1. Choose **Create access key**.
1. Choose **Download .csv file**.
## To configure the AWS CLI
After installing the AWS CLI, do the following steps to configure it. For more information, see [Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) in the * AWS Command Line Interface User Guide*.
1. In a terminal window, enter the following command:
```
aws configure
```
Optionally, you can configure a named profile, such as `--profile cluster-admin`. If you configure a named profile in the AWS CLI, you must **always** pass this flag in subsequent commands.
1. Enter your AWS credentials. For example:
```
Access Key ID [None]: AKIAIOSFODNN7EXAMPLE
Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Default region name [None]: region-code
Default output format [None]: json
```
## To get a security token
If needed, run the following command to get a new security token for the AWS CLI. For more information, see [get-session-token](https://docs.aws.amazon.com/cli/latest/reference/sts/get-session-token.html) in the * AWS CLI Command Reference*.
By default, the token is valid for 15 minutes. To change the default session timeout, pass the `--duration-seconds` flag. For example:
```
aws sts get-session-token --duration-seconds 3600
```
This command returns the temporary security credentials for an AWS CLI session. You should see the following response output:
```
{
"Credentials": {
"AccessKeyId": "ASIA5FTRU3LOEXAMPLE",
"SecretAccessKey": "JnKgvwfqUD9mNsPoi9IbxAYEXAMPLE",
"SessionToken": "VERYLONGSESSIONTOKENSTRING",
"Expiration": "2023-02-17T03:14:24+00:00"
}
}
```
## To verify the user identity
If needed, run the following command to verify the AWS credentials for your IAM user identity (such as *ClusterAdmin*) for the terminal session.
```
aws sts get-caller-identity
```
This command returns the Amazon Resource Name (ARN) of the IAM entity that’s configured for the AWS CLI. You should see the following example response output:
```
{
"UserId": "AKIAIOSFODNN7EXAMPLE",
"Account": "01234567890",
"Arn": "arn:aws:iam::01234567890:user/ClusterAdmin"
}
```
## Next steps
+ [Set up kubectl and eksctl](install-kubectl.md)
+ [Quickstart: Deploy a web app and store data](quickstart.md)
# Set up `kubectl` and `eksctl`
**Tip**
[Register](https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c&sc_channel=el) for upcoming Amazon EKS workshops.
Once the AWS CLI is installed, there are two other tools you should install to create and manage your Kubernetes clusters:
+ `kubectl`: The `kubectl` command line tool is the main tool you will use to manage resources within your Kubernetes cluster. This page describes how to download and set up the `kubectl` binary that matches the version of your Kubernetes cluster. See [Install or update kubectl](#kubectl-install-update).
+ `eksctl`: The `eksctl` command line tool is made for creating EKS clusters in the AWS cloud or on-premises (with EKS Anywhere), as well as modifying and deleting those clusters. See [Install eksctl](#eksctl-install-update).
## Install or update `kubectl`
This topic helps you to download and install, or update, the `kubectl` binary on your device. The binary is identical to the [upstream community versions](https://kubernetes.io/docs/tasks/tools/#kubectl). The binary is not unique to Amazon EKS or AWS. Use the steps below to get the specific version of `kubectl` that you need, although many builders simply run `brew install kubectl` to install it.
**Note**
You must use a `kubectl` version that is within one minor version difference of your Amazon EKS cluster control plane. For example, a `1.34` `kubectl` client works with Kubernetes `1.33`, `1.34`, and `1.35` clusters.
## Step 1: Check if `kubectl` is installed
Determine whether you already have `kubectl` installed on your device.
```
kubectl version --client
```
If you have `kubectl` installed in the path of your device, the example output includes information similar to the following. If you want to update the version that you currently have installed with a later version, complete the next step, making sure to install the new version in the same location that your current version is in.
```
Client Version: v1.31.X-eks-1234567
```
If you receive no output, then you either don’t have `kubectl` installed, or it’s not installed in a location that’s in your device’s path.
## Step 2: Install or update `kubectl`
Install or update `kubectl` on one of the following operating systems:
+ [macOS](#macos_kubectl)
+ [Linux (amd64)](#linux_amd64_kubectl)
+ [Linux (arm64)](#linux_arm64_kubectl)
+ [Windows](#windows_kubectl)
**Note**
If downloads are slow to your AWS Region from the AWS Regions used in this section, consider setting up CloudFront to front the content. For further information, see [Get started with a basic CloudFront distribution](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/GettingStartedSimpleDistributon.html).
### macOS
Follow the steps below to install `kubectl` on macOS. The steps include:
+ Choosing and downloading the binary for the Kubernetes version you want.
+ Optionally checking the binary’s checksum.
+ Adding execute to the binary’s permissions.
+ Copying the binary to a folder in your PATH.
+ Optionally adding the binary’s directory to your PATH.
Procedure:
1. Download the binary for your cluster’s Kubernetes version from Amazon S3.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/darwin/amd64/kubectl
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/darwin/amd64/kubectl
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/darwin/amd64/kubectl
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/darwin/amd64/kubectl
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/darwin/amd64/kubectl
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/darwin/amd64/kubectl
```
1. (Optional) Verify the downloaded binary with the `SHA-256` checksum for your binary.
1. Download the `SHA-256` checksum for your cluster’s Kubernetes version.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/darwin/amd64/kubectl.sha256
```
1. Check the `SHA-256` checksum for your downloaded binary.
```
openssl sha1 -sha256 kubectl
```
1. Make sure that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file.
1. Apply execute permissions to the binary.
```
chmod +x ./kubectl
```
1. Copy the binary to a folder in your `PATH`. If you have already installed a version of `kubectl`, then we recommend creating a `$HOME/bin/kubectl` and ensuring that `$HOME/bin` comes first in your `$PATH`.
```
mkdir -p $HOME/bin && cp ./kubectl $HOME/bin/kubectl && export PATH=$HOME/bin:$PATH
```
1. (Optional) Add the `$HOME/bin` path to your shell initialization file so that it is configured when you open a shell.
```
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bash_profile
```
### Linux (amd64)
Follow the steps below to install `kubectl` on Linux (amd64). The steps include:
+ Choosing and downloading the binary for the Kubernetes version you want.
+ Optionally checking the binary’s checksum.
+ Adding execute to the binary’s permissions.
+ Copying the binary to a folder in your PATH.
+ Optionally adding the binary’s directory to your PATH.
Procedure:
1. Download the `kubectl` binary for your cluster’s Kubernetes version from Amazon S3.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/linux/amd64/kubectl
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/linux/amd64/kubectl
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/linux/amd64/kubectl
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/linux/amd64/kubectl
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/linux/amd64/kubectl
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/linux/amd64/kubectl
```
1. (Optional) Verify the downloaded binary with the `SHA-256` checksum for your binary.
1. Download the `SHA-256` checksum for your cluster’s Kubernetes version from Amazon S3 using the command for your device’s hardware platform.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/linux/amd64/kubectl.sha256
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/linux/amd64/kubectl.sha256
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/linux/amd64/kubectl.sha256
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/linux/amd64/kubectl.sha256
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/linux/amd64/kubectl.sha256
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/linux/amd64/kubectl.sha256
```
1. Check the `SHA-256` checksum for your downloaded binary with one of the following commands.
```
sha256sum -c kubectl.sha256
```
or
```
openssl sha1 -sha256 kubectl
```
1. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file.
1. Apply execute permissions to the binary.
```
chmod +x ./kubectl
```
1. Copy the binary to a folder in your `PATH`. If you have already installed a version of `kubectl`, then we recommend creating a `$HOME/bin/kubectl` and ensuring that `$HOME/bin` comes first in your `$PATH`.
```
mkdir -p $HOME/bin && cp ./kubectl $HOME/bin/kubectl && export PATH=$HOME/bin:$PATH
```
1. (Optional) Add the `$HOME/bin` path to your shell initialization file so that it is configured when you open a shell.
**Note**
This step assumes you are using the Bash shell; if you are using another shell, change the command to use your specific shell initialization file.
```
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bashrc
```
### Linux (arm64)
Follow the steps below to install `kubectl` on Linux (arm64). The steps include:
+ Choosing and downloading the binary for the Kubernetes version you want.
+ Optionally checking the binary’s checksum.
+ Adding execute to the binary’s permissions.
+ Copying the binary to a folder in your PATH.
+ Optionally adding the binary’s directory to your PATH.
Procedure:
1. Download the `kubectl` binary for your cluster’s Kubernetes version from Amazon S3.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/linux/arm64/kubectl
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/linux/arm64/kubectl
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/linux/arm64/kubectl
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/linux/arm64/kubectl
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/linux/arm64/kubectl
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/linux/arm64/kubectl
```
1. (Optional) Verify the downloaded binary with the `SHA-256` checksum for your binary.
1. Download the `SHA-256` checksum for your cluster’s Kubernetes version from Amazon S3 using the command for your device’s hardware platform.
+ Kubernetes `1.35`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/linux/arm64/kubectl.sha256
```
+ Kubernetes `1.34`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/linux/arm64/kubectl.sha256
```
+ Kubernetes `1.33`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/linux/arm64/kubectl.sha256
```
+ Kubernetes `1.32`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/linux/arm64/kubectl.sha256
```
+ Kubernetes `1.31`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/linux/arm64/kubectl.sha256
```
+ Kubernetes `1.30`
```
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/linux/arm64/kubectl.sha256
```
1. Check the `SHA-256` checksum for your downloaded binary with one of the following commands.
```
sha256sum -c kubectl.sha256
```
or
```
openssl sha1 -sha256 kubectl
```
1. For the first, you should see `kubectl: OK`, for the second, you can check that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file.
1. Apply execute permissions to the binary.
```
chmod +x ./kubectl
```
1. Copy the binary to a folder in your `PATH`. If you have already installed a version of `kubectl`, then we recommend creating a `$HOME/bin/kubectl` and ensuring that `$HOME/bin` comes first in your `$PATH`.
```
mkdir -p $HOME/bin && cp ./kubectl $HOME/bin/kubectl && export PATH=$HOME/bin:$PATH
```
1. (Optional) Add the `$HOME/bin` path to your shell initialization file so that it is configured when you open a shell.
**Note**
This step assumes you are using the Bash shell; if you are using another shell, change the command to use your specific shell initialization file.
```
echo 'export PATH=$HOME/bin:$PATH' >> ~/.bashrc
```
### Windows
Follow the steps below to install `kubectl` on Windows. The steps include:
+ Choosing and downloading the binary for the Kubernetes version you want.
+ Optionally checking the binary’s checksum.
+ Copying the binary to a folder in your PATH.
+ Optionally adding the binary’s directory to your PATH.
Procedure:
1. Open a PowerShell terminal.
1. Download the `kubectl` binary for your cluster’s Kubernetes version from Amazon S3.
+ Kubernetes `1.35`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/windows/amd64/kubectl.exe
```
+ Kubernetes `1.34`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/windows/amd64/kubectl.exe
```
+ Kubernetes `1.33`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/windows/amd64/kubectl.exe
```
+ Kubernetes `1.32`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/windows/amd64/kubectl.exe
```
+ Kubernetes `1.31`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/windows/amd64/kubectl.exe
```
+ Kubernetes `1.30`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/windows/amd64/kubectl.exe
```
1. (Optional) Verify the downloaded binary with the `SHA-256` checksum for your binary.
1. Download the `SHA-256` checksum for your cluster’s Kubernetes version for Windows.
+ Kubernetes `1.35`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.35.3/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
+ Kubernetes `1.34`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.6/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
+ Kubernetes `1.33`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.33.10/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
+ Kubernetes `1.32`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.32.13/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
+ Kubernetes `1.31`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.31.14/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
+ Kubernetes `1.30`
```
curl.exe -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.14/2026-04-08/bin/windows/amd64/kubectl.exe.sha256
```
1. Check the `SHA-256` checksum for your downloaded binary.
```
Get-FileHash kubectl.exe
```
1. Make sure that the generated checksum in the output matches in the checksum in the downloaded `kubectl.sha256` file. The PowerShell output should be an uppercase equivalent string of characters.
1. Copy the binary to a folder in your `PATH`. If you have an existing directory in your `PATH` that you use for command line utilities, copy the binary to that directory. Otherwise, complete the following steps.
1. Create a new directory for your command line binaries, such as `C:\bin`.
1. Copy the `kubectl.exe` binary to your new directory.
1. Edit your user or system `PATH` environment variable to add the new directory to your `PATH`.
1. Close your PowerShell terminal and open a new one to pick up the new `PATH` variable.
1. After you install `kubectl`, you can verify its version.
```
kubectl version --client
```
1. When first installing `kubectl`, it isn’t yet configured to communicate with any server. We will cover this configuration as needed in other procedures. If you ever need to update the configuration to communicate with a particular cluster, you can run the following command. Replace *region-code* with the AWS Region that your cluster is in. Replace *my-cluster* with the name of your cluster.
```
aws eks update-kubeconfig --region region-code --name my-cluster
```
1. Consider configuring auto completion, which lets you use the tab key to complete `kubectl` subcommands after typing the first few letters. See [Kubectl autocomplete](https://kubernetes.io/docs/reference/kubectl/quick-reference/#kubectl-autocomplete) in the Kubernetes documentation for details.
## Install `eksctl`
The `eksctl` CLI is used to work with EKS clusters. It automates many individual tasks. See [Installation](https://eksctl.io/installation) in the `eksctl` documentation for instructions on installing `eksctl`. For Linux, use the UNIX instructions.
When using `eksctl` the IAM security principal that you’re using must have permissions to work with Amazon EKS IAM roles, service linked roles, AWS CloudFormation, a VPC, and related resources. For more information, see [Actions](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonelastickubernetesservice.html) and [Using service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) in the IAM User Guide. You must complete all steps in this guide as the same user. To check the current user, run the following command:
```
aws sts get-caller-identity
```
## Next steps
+ [Quickstart: Deploy a web app and store data](quickstart.md)