### Example Controller Deployment Output Source: https://docs.aws.amazon.com/eks/latest/userguide/lbc-manifest.md This is an example of the expected output when verifying the controller deployment. The number of replicas may vary based on the installation method (Helm vs. manifest). ```text NAME READY UP-TO-DATE AVAILABLE AGE aws-load-balancer-controller 2/2 2 2 84s ``` -------------------------------- ### Example kubectl Client Version Output Source: https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.md This is an example of the output you might see if kubectl is installed and configured correctly. ```text Client Version: v1.31.X-eks-1234567 ``` -------------------------------- ### Example Metrics Server Deployment Output Source: https://docs.aws.amazon.com/eks/latest/userguide/metrics-server.md This is an example output for the 'kubectl get deployment metrics-server -n kube-system' command, indicating a successful deployment. ```text NAME READY UP-TO-DATE AVAILABLE AGE metrics-server 1/1 1 1 6m ``` -------------------------------- ### Example: Retrieve Windows Server 2022 Core AMI ID Source: https://docs.aws.amazon.com/eks/latest/userguide/retrieve-windows-ami-id.md This is an example of the command after replacing placeholders for Windows Server 2022, Server Core installation, a specific Kubernetes version, and the us-west-2 region. ```bash aws ssm get-parameter --name /aws/service/ami-windows-latest/Windows_Server-{{2022}}-English-{{Core}}-EKS_Optimized-{{k8s-n-2}}/image_id \ --region {{us-west-2}} --query "Parameter.Value" --output text ``` -------------------------------- ### Sample Request to List Add-ons Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_ListAddons.md This snippet shows an example HTTP GET request to list add-ons for a specific EKS cluster. Ensure the Host and X-Amz-Date headers are correctly set. ```http GET /clusters/1-18/addons HTTP/1.1 Host: eks.us-west-2.amazonaws.com Accept-Encoding: identity User-Agent: aws-cli/1.16.298 Python/3.6.0 Windows/10 botocore/1.13.34 X-Amz-Date: 20201125T144629Z Authorization: AUTHPARAMS ``` -------------------------------- ### Sample Request for DescribeAddon Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddon.md This snippet shows an example HTTP GET request to describe an EKS addon. It includes necessary headers like Host, Accept-Encoding, User-Agent, X-Amz-Date, and Authorization. ```http GET /clusters/1-18/addons/vpc-cni HTTP/1.1 Host: eks.us-west-2.amazonaws.com Accept-Encoding: identity User-Agent: aws-cli/1.16.298 Python/3.6.0 Windows/10 botocore/1.13.34 X-Amz-Date: 20201125T144831Z Authorization: AUTHPARAMS ``` -------------------------------- ### Start packet capture with start-capture.py Source: https://docs.aws.amazon.com/eks/latest/userguide/auto-get-tcpdump.md Run the start-capture.py script to initiate network traffic capture. This script requires Python 3 with boto3 and pyyaml installed, and kubectl configured for your cluster. Replace {{}} and {{}} with your values. ```python python3 start-capture.py --bucket {{}} --node {{}} ``` -------------------------------- ### Example Helm Version Output Source: https://docs.aws.amazon.com/eks/latest/userguide/helm.md This is an example of the output you can expect when checking the Helm version. ```text v3.17.2 ``` -------------------------------- ### Example CoreDNS Version Output Source: https://docs.aws.amazon.com/eks/latest/userguide/coredns-add-on-create.md This is an example output showing the version of the CoreDNS add-on. ```text v1.10.1-eksbuild.1 ``` -------------------------------- ### Build a static binary from scratch using Go Source: https://docs.aws.amazon.com/eks/latest/best-practices/image-security.md This example demonstrates how to build a statically linked binary using Go and a minimal base image, which can then be used in a Dockerfile to create a lean container image. ```dockerfile ############################ # STEP 1 build executable binary ############################ FROM golang:alpine AS builder# Install git. # Git is required for fetching the dependencies. RUN apk update && apk add --no-cache gitWORKDIR $GOPATH/src/mypackage/myapp/COPY . . # Fetch dependencies. # Using go get. RUN go get -d -v# Build the binary. RUN go build -o /go/bin/hello ``` -------------------------------- ### Cluster Autoscaler Deployment Example Source: https://docs.aws.amazon.com/eks/latest/best-practices/cas.md This is a typical Kubernetes Deployment manifest for installing the Cluster Autoscaler. Ensure the version matches your EKS cluster version. Auto-discovery is recommended for most setups. ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: cluster-autoscaler namespace: kube-system labels: app: cluster-autoscaler spec: replicas: 1 selector: matchLabels: app: cluster-autoscaler template: metadata: labels: app: cluster-autoscaler spec: containers: - name: cluster-autoscaler image: registry.k8s.io/autoscaling/cluster-autoscaler:v1.27.0 resources: limits: cpu: 100m memory: 300Mi requests: cpu: 100m memory: 300Mi command: - /cluster-autoscaler - --v=4 - --stderrthreshold=info - --cloud-provider=aws - --skip-nodes-with-local-storage=false - --nodes= min-cluster-size=1 max-cluster-size=10 # The following flags are specific to the AWS cloud provider. # Please use the AWS provider documentation for more information. # --aws-cluster-autoscaler:enabled # --aws-tag-specification "ResourceGroups:" "IgnoredDuringDiscovery" # --aws-zones=us-west-2a,us-west-2b,us-west-2c # --aws-vpc-tags="k8s.io/cluster-autoscaler/enabled=true" # --aws-node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,k8s.io/cluster-autoscaler/my-cluster # --aws-balance-attached-groups=true # --aws-enable-pod-anti-affinity=true # --aws-max-pods-per-node=30 # --aws-prefer-attached-groups=true # --aws-service-account-token-file=/run/secrets/kubernetes.io/serviceaccount/token # --aws-signing-region=us-west-2 # --aws-tag-auto-created-by=true # --aws-tag-cluster-name=true # --aws-tag-nodegroup-name=true # --aws-use-static-instance-list=false # --aws-utilization-threshold=0.5 volumeMounts: - name: k8s-certs mountPath: /etc/kubernetes/pki - name: cloud-config mountPath: /etc/kubernetes/cloudconfig imagePullPolicy: Always volumes: - name: k8s-certs hostPath: path: /etc/kubernetes/pki - name: cloud-config secret: secretName: cluster-autoscaler-aws-credentials ``` -------------------------------- ### Example kubectl get svc output Source: https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.md This is an example of the expected output when testing your kubectl configuration by listing services. ```text NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/kubernetes ClusterIP 10.100.0.1 443/TCP 1m ``` -------------------------------- ### Addon Details Output Example Source: https://docs.aws.amazon.com/eks/latest/eksctl/addons.md Example output showing addon details retrieved in YAML format, including configuration values. ```yaml - ConfigurationValues: '{"replicaCount":3}' IAMRole: "" Issues: null Name: coredns NewerVersion: "" Status: ACTIVE Version: v1.8.7-eksbuild.3 ``` -------------------------------- ### View Build Help and Options Source: https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-build-scripts.md Display available build targets, variables, and options for customizing AMI builds by running the 'make help' command. ```bash make help ``` -------------------------------- ### Example Output of Pod Status Source: https://docs.aws.amazon.com/eks/latest/userguide/cni-network-policy-configure.md This is an example of the output from the 'kubectl get pods' command, showing running aws-node pods. ```text aws-node-gmqp7 2/2 Running 1 (24h ago) 24h aws-node-prnsh 2/2 Running 1 (24h ago) 24h ``` -------------------------------- ### Deploy Sample Application Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-ingress.md Apply a sample application manifest to your Kubernetes cluster. This example uses the Istio Bookinfo application. ```bash kubectl apply -f https://raw.githubusercontent.com/istio/istio/refs/heads/master/samples/bookinfo/platform/kube/bookinfo.yaml ``` -------------------------------- ### Example EKS Connector Pod Status Output Source: https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting-connector.md Example output from 'kubectl get pods -n eks-connector' showing a Pod in Init:CrashLoopBackOff status. ```text NAME READY STATUS RESTARTS AGE eks-connector-0 0/2 Init:CrashLoopBackOff 1 7s ``` -------------------------------- ### Example Node Status Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-cni.md Example output showing a hybrid node with `Ready` status and its Kubernetes version. ```text NAME STATUS ROLES AGE VERSION mi-04a2cf999b7112233 Ready 19m v1.31.0-eks-a737599 ``` -------------------------------- ### Example output of 'yum whatprovides ps' Source: https://docs.aws.amazon.com/eks/latest/userguide/auto-troubleshoot.md This is an example output showing the packages that provide the 'ps' command, including version and repository information. ```text Last metadata expiration check: 0:03:36 ago on Thu Jan 16 14:49:17 2025. procps-ng-3.3.17-1.amzn2023.0.2.x86_64 : System and process monitoring utilities Repo : @System Matched from: Filename : /usr/bin/ps Provide : /bin/ps procps-ng-3.3.17-1.amzn2023.0.2.x86_64 : System and process monitoring utilities Repo : amazonlinux Matched from: Filename : /usr/bin/ps Provide : /bin/ps ``` -------------------------------- ### Example GPU Operator Pods Output Source: https://docs.aws.amazon.com/eks/latest/best-practices/aiml-compute.md Example output from 'kubectl get pods -n gpu-operator', showing the status of various GPU Operator components. ```text NAME READY STATUS RESTARTS AGE gpu-feature-discovery-27rdq 1/1 Running 0 3h31m gpu-operator-555774698d-48brn 1/1 Running 0 4h8m nvidia-container-toolkit-daemonset-sxmh9 1/1 Running 1 (3h32m ago) 4h1m nvidia-cuda-validator-qb77g 0/1 Completed 0 3h31m nvidia-dcgm-exporter-cvzd7 1/1 Running 0 3h31m nvidia-device-plugin-daemonset-5ljm5 1/1 Running 0 3h31m nvidia-gpu-operator-node-feature-discovery-gc-67f66fc557-q5wkt 1/1 Running 0 4h8m nvidia-gpu-operator-node-feature-discovery-master-5d8ffddcsl6s6 1/1 Running 0 4h8m nvidia-gpu-operator-node-feature-discovery-worker-6t4w7 1/1 Running 1 (3h32m ago) 4h1m nvidia-gpu-operator-node-feature-discovery-worker-9w7g8 1/1 Running 0 4h8m nvidia-gpu-operator-node-feature-discovery-worker-k5fgs 1/1 Running 0 4h8m nvidia-mig-manager-zvf54 1/1 Running 1 (3h32m ago) 3h35m ``` -------------------------------- ### Example Storage Class Creation Output Source: https://docs.aws.amazon.com/eks/latest/userguide/fsx-csi-create.md This is an example of the output you might see after successfully creating a storage class. ```text storageclass.storage.k8s.io/fsx-sc created ``` -------------------------------- ### Example Pod DNS Configuration Output Source: https://docs.aws.amazon.com/eks/latest/userguide/sample-deployment.md An example of the output from the /etc/resolv.conf file within an EKS Pod, illustrating the nameserver and search options. ```text nameserver 10.100.0.10 search eks-sample-app.svc.cluster.local svc.cluster.local cluster.local us-west-2.compute.internal options ndots:5 ``` -------------------------------- ### SSM Setup CLI Checksum Mismatch Error Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-troubleshooting.md This error indicates a potential issue with existing SSM installations. Ensure older versions are removed before re-running the installation command. ```text Failed to perform agent-installation/on-prem registration: error while verifying installed ssm-setup-cli checksum: checksum mismatch with latest ssm-setup-cli. ``` -------------------------------- ### Example EKS Connector Pod Status Source: https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting-connector.md Example output from 'kubectl get pods' showing a Pod in the Init:ImagePullBackOff state. This indicates an issue pulling container images. ```bash NAME READY STATUS RESTARTS AGE eks-connector-0 0/2 Init:ImagePullBackOff 0 4s ``` -------------------------------- ### Addon Details with Namespace Output Example Source: https://docs.aws.amazon.com/eks/latest/eksctl/addons.md Example output showing addon details including the custom namespace configuration. ```yaml - ConfigurationValues: "" IAMRole: "" Issues: null Name: aws-ebs-csi-driver NamespaceConfig: namespace: custom-namespace NewerVersion: "" PodIdentityAssociations: null Status: ACTIVE Version: v1.47.0-eksbuild.1 ``` -------------------------------- ### Display Web Server Output Example Source: https://docs.aws.amazon.com/eks/latest/userguide/sample-deployment-win.md This is an example of the output you might see when checking the web server content from within the Pod shell. ```text StatusCode : 200 StatusDescription : OK Content : < h t m l > < b o d y > < b r / > < b r / > < m a r q u e e > < H 1 > H e l l o E K S ! ! ! < H 1 > < m a r q u e e > < / b o d y > < h t m l > ``` -------------------------------- ### Example Output of Verified Service Source: https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.md This is an example output of the 'kubectl get svc' command, illustrating the structure and key information, including the EXTERNAL-IP which is the NLB's DNS name. ```text NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE sample-service LoadBalancer 10.100.240.137 k8s-nlbsampl-nlbsampl-xxxxxxxxxx-xxxxxxxxxxxxxxxx.elb.region-code.amazonaws.com 80:32400/TCP 16h ``` -------------------------------- ### List all running pods with limit Source: https://docs.aws.amazon.com/eks/latest/best-practices/scale-control-plane.md This example shows how to list all running pods across all namespaces, applying a limit to the results. It's useful for monitoring active pods efficiently. ```bash /api/v1/pods?fieldSelector=status.phase=Running&limit=500 ``` -------------------------------- ### ListAddons API Example Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_ListAddons.md Provides an example of how to list the add-ons installed to an Amazon EKS cluster. It also includes important notes on authentication using AWS Signature Version 4. ```APIDOC ## Examples In the following example or examples, the Authorization header contents (`AUTHPARAMS`) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see [Signature Version 4 Signing Process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) in the *Amazon EKS General Reference*. You need to learn how to sign HTTP requests only if you intend to manually create them. When you use the [AWS Command Line Interface (AWS CLI)](http://aws.amazon.com/cli/) or one of the [AWS SDKs](http://aws.amazon.com/tools/) to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself. ### Example The following example lists the add-ons installed to a cluster. ``` -------------------------------- ### Deploy Sample Application Source: https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.md Save this content to a file named `sample-app.yaml` to deploy a sample NGINX application. ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: sample-app namespace: {{same-namespace-as-your-fargate-profile}} spec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:latest ports: - name: http containerPort: 80 ``` -------------------------------- ### Get Hamster Pods Source: https://docs.aws.amazon.com/eks/latest/userguide/vertical-pod-autoscaler.md Retrieve the Pods belonging to the hamster example application to check their status. ```bash kubectl get pods -l app=hamster ``` -------------------------------- ### Example File System Mount Output Source: https://docs.aws.amazon.com/eks/latest/userguide/fsx-csi-create.md This output shows an example of the file system mount information within the application pod, confirming the FSx for Lustre mount point. ```text Filesystem Size Used Avail Use% Mounted on overlay 80G 4.0G 77G 5% / tmpfs 64M 0 64M 0% /dev tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup 192.0.2.0@tcp:/abcdef01 1.1T 7.8M 1.1T 1% /data /dev/nvme0n1p1 80G 4.0G 77G 5% /etc/hosts shm 64M 0 64M 0% /dev/shm tmpfs 6.9G 12K 6.9G 1% /run/secrets/kubernetes.io/serviceaccount tmpfs 3.8G 0 3.8G 0% /proc/acpi tmpfs 3.8G 0 3.8G 0% /sys/firmware ``` -------------------------------- ### Get VPC CNI Version Source: https://docs.aws.amazon.com/eks/latest/userguide/cni-network-policy-configure.md Check the currently installed version of the VPC CNI plugin on your cluster. ```bash kubectl describe daemonset aws-node --namespace kube-system | grep amazon-k8s-cni: | cut -d : -f 3 ``` -------------------------------- ### Example Confirmed CoreDNS Version Source: https://docs.aws.amazon.com/eks/latest/userguide/coredns-add-on-create.md This is an example output confirming the successfully created CoreDNS add-on version. ```text v1.11.3-eksbuild.1 ``` -------------------------------- ### Sample StartInsightsRefresh API Request Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_StartInsightsRefresh.md Example of a POST request to start the cluster insights generation process. ```HTTP POST /clusters/name/insights-refresh HTTP/1.1 ``` -------------------------------- ### Get Help for eksctl create addon Source: https://docs.aws.amazon.com/eks/latest/userguide/creating-an-add-on.md This command displays all available options and arguments for the `eksctl create addon` command, aiding in customization and troubleshooting. ```bash eksctl create addon --help ``` -------------------------------- ### Example Output of Agent Pods Source: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.md This is an example output from the `kubectl get pods` command, showing the status of the EKS Pod Identity Agent pods. It indicates that the pods are running and provides details about their status and age. ```bash eks-pod-identity-agent-gmqp7 1/1 Running 1 (24h ago) 24h eks-pod-identity-agent-prnsh 1/1 Running 1 (24h ago) 24h ``` -------------------------------- ### Deploy Sample Application Source: https://docs.aws.amazon.com/eks/latest/userguide/fsx-csi-create.md Apply the sample application manifest to your Kubernetes cluster. This will create the necessary resources for testing FSx for Lustre. ```bash kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-fsx-csi-driver/master/examples/kubernetes/dynamic_provisioning/specs/pod.yaml ``` -------------------------------- ### Extend nodeadm install timeout Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-troubleshooting.md When `nodeadm install` encounters timeouts due to slow connections, use the `--timeout` flag to increase the duration for downloading dependencies. Specify the desired duration, for example, `20m0s` for 20 minutes. ```bash nodeadm install K8S_VERSION --credential-provider CREDS_PROVIDER --timeout {{20m0s}} ``` -------------------------------- ### Get mutating webhook configurations Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-webhooks.md Use this command to list all mutating webhook configurations in your cluster. This helps in understanding the webhook setup for your applications. ```bash kubectl get mutatingwebhookconfigurations ``` -------------------------------- ### Get SSM Agent Version Source: https://docs.aws.amazon.com/eks/latest/best-practices/hybrid-nodes-host-creds.md Check the installed version of the SSM agent on AL2023 and RHEL systems, or on Ubuntu systems using snap. ```bash # AL2023, RHEL yum info amazon-ssm-agent # Ubuntu snap list amazon-ssm-agent ``` -------------------------------- ### Advanced start-capture.py options Source: https://docs.aws.amazon.com/eks/latest/userguide/auto-get-tcpdump.md These examples show advanced usage of the start-capture.py script, including specifying capture duration, interface, filter, and performing a dry run to preview the YAML without applying it. ```python # Capture for 5 minutes on eth0 with a filter python3 start-capture.py --bucket {{}} --node {{}} \ --duration 5m --interface eth0 --filter "tcp port 443" # Preview the YAML without applying python3 start-capture.py --bucket {{}} --node {{}} --dry-run ``` -------------------------------- ### Create Namespace for Sample Application Source: https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.md Creates a Kubernetes namespace to host the sample application. This is a prerequisite for deploying the application. ```bash kubectl create namespace nlb-sample-app ``` -------------------------------- ### AL2023 User Data Example Source: https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.md This is a complete example of AL2023 user data that combines a shell script for customizing the node with the required nodeadm configuration. It demonstrates installing system packages, pre-caching container images, setting up HTTP proxy, and configuring kubelet flags. ```shell MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="BOUNDARY" --BOUNDARY Content-Type: text/x-shellscript; charset="us-ascii" #!/bin/bash set -o errexit set -o pipefail set -o nounset ``` -------------------------------- ### All Supported IAM Add-on Policies Example Source: https://docs.aws.amazon.com/eks/latest/eksctl/iam-policies.md This example demonstrates how to enable multiple IAM add-on policies for a node group, including image builder, auto scaler, external DNS, and more. ```yaml nodeGroups: - name: ng-1 instanceType: m5.xlarge desiredCapacity: 1 iam: withAddonPolicies: imageBuilder: true autoScaler: true externalDNS: true certManager: true appMesh: true appMeshPreview: true ebs: true fsx: true efs: true awsLoadBalancerController: true xRay: true cloudWatch: true ``` -------------------------------- ### Get Predefined Namespace for an Add-on Source: https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.md Use this AWS CLI command to retrieve the default Kubernetes namespace where an add-on will be installed if no custom namespace is specified. ```bash aws eks describe-addon-versions --addon-name --query "addons[].defaultNamespace" ``` -------------------------------- ### Get Current CoreDNS Image Version Source: https://docs.aws.amazon.com/eks/latest/userguide/coredns-add-on-self-managed-update.md Retrieves the current CoreDNS container image version installed on your cluster. This helps in identifying the version before an update. ```bash kubectl describe deployment coredns -n kube-system | grep Image | cut -d ":" -f 3 ``` -------------------------------- ### Get Envoy Listener Port Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-ingress.md Obtain the Envoy listener port for the 'cilium-ingress' Service using a JSONPath expression. The example assumes the shared listener port is 8111. ```bash kubectl get cec -n kube-system cilium-ingress -o jsonpath={.spec.services[0].ports[0]} ``` -------------------------------- ### Create EKS Resources Source: https://docs.aws.amazon.com/eks/latest/userguide/eks-mcp-introduction.md These commands demonstrate how to create EKS clusters, deploy applications, and generate Kubernetes deployment YAMLs. ```bash Create a new EKS cluster named demo-cluster with VPC and Auto Mode Deploy my containerized app from ECR to the production namespace with 3 replicas Generate a Kubernetes deployment YAML for my Node.js app running on port 3000 ``` -------------------------------- ### EKS Insight Recommendation Example Source: https://docs.aws.amazon.com/eks/latest/best-practices/cluster-upgrades.md This JSON snippet provides a recommended action for an EKS cluster insight, guiding users on necessary steps before upgrading Kubernetes versions. ```json "recommendation": "Update manifests and API clients to use newer Kubernetes APIs if applicable before upgrading to Kubernetes v1.26." ``` -------------------------------- ### Example Pod Status Output Source: https://docs.aws.amazon.com/eks/latest/userguide/fsx-csi-create.md This is an example of the expected output when verifying the sample application's pod status. ```text NAME READY STATUS RESTARTS AGE fsx-app 1/1 Running 0 8s ``` -------------------------------- ### List Amazon EKS Clusters Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_ListClusters.md Lists all Amazon EKS clusters in the specified AWS Region. This example shows a sample HTTP GET request and its corresponding JSON response. ```HTTP GET /clusters HTTP/1.1 Host: eks.us-west-2.amazonaws.com Accept-Encoding: identity User-Agent: aws-cli/1.15.0 Python/3.6.5 Darwin/16.7.0 botocore/1.10.0 X-Amz-Date: 20180531T231200Z Authorization: AUTHPARAMS ``` ```HTTP HTTP/1.1 200 OK Date: Thu, 31 May 2018 23:12:00 GMT Content-Type: application/json Content-Length: 46 x-amzn-RequestId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx x-amz-apigw-id: HxkiCF8EPHcF4nw= X-Amzn-Trace-Id: Root=1-xxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx Connection: keep-alive { "clusters": [ "my-cluster", "prod" ], "nextToken": null } ``` -------------------------------- ### Example Output for Insights Refresh Status Source: https://docs.aws.amazon.com/eks/latest/userguide/view-cluster-insights.md Illustrates the expected JSON output when checking the status of an EKS cluster insights refresh, indicating the current state and start time. ```json { "message": "Insights refresh is in progress", "status": "IN_PROGRESS", "startedAt": "2025-07-30T13:36:09-07:00" } ``` -------------------------------- ### Example: List Available Access Policies Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_ListAccessPolicies.md This example demonstrates how to list the available access policies for an Amazon EKS cluster. Ensure you replace placeholder values and sign the request. ```HTTP GET /access-policies?maxResults=10&nextToken=string HTTP/1.1 Host: eks.us-east-1.amazonaws.com Authorization: AUTHPARAMS ``` -------------------------------- ### DescribeAddon Example Source: https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddon.md This section provides an example of how to describe an add-on using the DescribeAddon API. It includes instructions on authentication and a sample request. ```APIDOC ## Examples In the following example or examples, the Authorization header contents (`AUTHPARAMS`) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see [Signature Version 4 Signing Process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) in the *Amazon EKS General Reference*. You need to learn how to sign HTTP requests only if you intend to manually create them. When you use the [AWS Command Line Interface (AWS CLI)](http://aws.amazon.com/cli/) or one of the [AWS SDKs](http://aws.amazon.com/tools/) to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself. ### Example The following example describes an add-on named `vpc-cni`. ``` -------------------------------- ### Start SSM Session to Access EKS Node Source: https://docs.aws.amazon.com/eks/latest/best-practices/protecting-the-infrastructure.md Use this AWS CLI command to initiate a session with an EKS node after applying the minimal IAM policy and installing the Session Manager plugin. ```bash aws ssm start-session --target [INSTANCE_ID_OF_EKS_NODE] ``` -------------------------------- ### Example Output of NGINX Welcome Page Source: https://docs.aws.amazon.com/eks/latest/userguide/hybrid-nodes-load-balancing.md This is an example of the output you might receive when accessing the NGINX service via the NLB. It shows the basic HTML response from the NGINX server. ```html Welcome to nginx! [...] ```