AWS eks documentation change

Service: eks · 2026-05-01 · Documentation low

File: eks/latest/userguide/create-kubeconfig.md

Summary

Updated documentation to add CloudShell connectivity option and restructured content to separate console-based connection from CLI-based kubeconfig creation

Security assessment

This change adds documentation for a new feature (CloudShell connectivity) and reorganizes existing content. There is no evidence of security vulnerability fixes or security feature additions. The change mentions CloudShell can connect to clusters with private endpoints via VPC environment, which is a feature enhancement, not a security fix.

Diff

diff --git a/eks/latest/userguide/create-kubeconfig.md b/eks/latest/userguide/create-kubeconfig.md
index f44a58cb5..b8e4f2303 100644
--- a//eks/latest/userguide/create-kubeconfig.md
+++ b//eks/latest/userguide/create-kubeconfig.md
@@ -7 +7 @@
-Create kubeconfig file automatically
+Connect using the EKS console (CloudShell)Create kubeconfig file using the AWS CLI
@@ -39 +39,24 @@ Amazon EKS uses the `aws eks get-token` command with `kubectl` for cluster authe
-## Create `kubeconfig` file automatically
+## Connect using the EKS console (CloudShell)
+
+You can connect to your cluster directly from the AWS Management Console using AWS CloudShell, without any local setup.
+
+  1. Open the Amazon EKS console at [https://console.aws.amazon.com/eks/home#/clusters](https://console.aws.amazon.com/eks/home#/clusters).
+
+  2. Choose the name of the cluster you want to connect to.
+
+  3. On the cluster details page, choose **Connect** from the top-right action bar.
+
+  4. AWS CloudShell opens with `kubectl` pre-configured for your cluster.
+
+
+
+
+Once connected, you can run `kubectl` commands immediately:
+    
+    
+    kubectl get nodes
+    kubectl get pods -A
+
+CloudShell sessions include `kubectl`, the AWS CLI, and standard CloudShell utilities. This feature supports clusters with both public and private API server endpoints. For clusters with private endpoints, CloudShell automatically launches a VPC environment to reach your cluster’s private API server and prompts you to enter a name for the environment.
+
+## Create `kubeconfig` file using the AWS CLI