awscli 1.40.17__py3-none-any.whl → 1.44.26__py3-none-any.whl

awscli/examples/cloudfront/update-distribution-tenant.rst

@@ -0,0 +1,76 @@
+**To update a CloudFront distribution tenant**
+
+The following ``update-distribution-tenant`` example updates a CloudFront distribution tenant with a new parameter value and adds a country to the geo-restrictions. ::
+
+    aws cloudfront update-distribution-tenant \
+        --cli-input-json file://update-tenant.json
+
+Contents of ``update-tenant.json``::
+
+    {
+        "Id": "dt_2yMvQgam3QkJo2z54FDl91dk1AB",
+        "IfMatch": "E1F83G8C2ARABC",
+        "Parameters": [
+            {
+                "Name": "testParam",
+                "Value": "newParameterValue"
+            }
+        ],
+        "Customizations": {
+            "WebAcl": {
+                "Action": "disable"
+            },
+            "GeoRestrictions": {
+                "RestrictionType": "whitelist",
+                "Locations": [
+                    "DE",
+                    "GB",
+                    "ES"
+                ]
+            }
+        }
+    }
+
+Output::
+
+    {
+        "ETag": "E1PA6795UKMABC",
+        "DistributionTenant": {
+            "Id": "dt_2yMvQgam3QkJo2z54FDl91dk1AB",
+            "DistributionId": "E1XNX8R2GOAABC",
+            "Name": "new-tenant-customizations",
+            "Arn": "arn:aws:cloudfront::123456789012:distribution-tenant/dt_2yMvQgam3QkJo2z54FDl91dk1AB",
+            "Domains": [
+                {
+                    "Domain": "example.com",
+                    "Status": "active"
+                }
+            ],
+            "Customizations": {
+                "WebAcl": {
+                    "Action": "disable"
+                },
+                "GeoRestrictions": {
+                    "RestrictionType": "whitelist",
+                    "Locations": [
+                        "DE",
+                        "ES",
+                        "GB"
+                    ]
+                }
+            },
+            "Parameters": [
+                {
+                    "Name": "testParam",
+                    "Value": "newParameterValue"
+                }
+            ],
+            "ConnectionGroupId": "cg_2whCJoXMYCjHcxaLGrkllvyABC",
+            "CreatedTime": "2025-06-11T15:54:02.142000+00:00",
+            "LastModifiedTime": "2025-06-11T16:42:45.531000+00:00",
+            "Enabled": false,
+            "Status": "InProgress"
+        }
+    }
+
+For more information, see `Distribution tenant customizations <https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/tenant-customization.html>`__ in the *Amazon CloudFront Developer Guide*.

awscli/examples/cloudfront/update-domain-association.rst

@@ -0,0 +1,18 @@
+**To update a domain association**
+
+The following ``update-domain-association`` example updates a domain association for a distribution tenant with ETag ``E23ZP02F085ABC``. ::
+
+    aws cloudfront update-domain-association \
+        --domain example.com \
+        --target-resource DistributionTenantId=dt_2x9GhoK0TZRsohWzv1b9It8J1AB \
+        --if-match E23ZP02F085ABC
+
+Output::
+
+    {
+        "ETag": "ETVPDKIKX0ABC",
+        "Domain": "example.com",
+        "ResourceId": "dt_2x9GhoK0TZRsohWzv1b9It8J1AB"
+    }
+
+For more information, see `Move an alternate domain name to a different distribution <https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/alternate-domain-names-move.html>`__ in the *Amazon CloudFront Developer Guide*.

awscli/examples/cloudfront/verify-dns-configuration.rst

@@ -0,0 +1,20 @@
+**To verify DNS configuration for a domain**
+
+The following ``verify-dns-configuration`` example verifies the DNS configuration for a domain. ::
+
+    aws cloudfront verify-dns-configuration \
+        --domain example.com \
+        --identifier dt_2x9GhoK0TZRsohWzv1b9It8J1AB
+
+Output::
+
+    {
+        "DnsConfigurationList": [
+            {
+                "Domain": "example.com",
+                "Status": "valid-configuration"
+            }
+        ]
+    }
+
+For more information, see `Move an alternate domain name to a different distribution <https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/alternate-domain-names-move.html>`__ in the *Amazon CloudFront Developer Guide*.

awscli/examples/ec2/associate-ipam-resource-discovery.rst

@@ -4,7 +4,7 @@ In this example, you are an IPAM delegated admin and a resource discovery has be
 
 Note
 
-* To complete this request, you'll need the resource discovery ID which you can get with `describe-ipam-resource-discoveries <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__ and the IPAM ID which you can get with `describe-ipams <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipams.html>`__.
+* To complete this request, you'll need the resource discovery ID which you can get with `describe-ipam-resource-discoveries <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__ and the IPAM ID which you can get with `describe-ipams <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipams.html>`__.
 * The resource discovery that you are associating must have first been shared with your account using AWS RAM.
 * The ``--region`` you enter must match the home Region of the IPAM you are associating it with.
 

awscli/examples/ec2/authorize-security-group-ingress.rst

@@ -63,7 +63,7 @@ The following ``authorize-security-group-ingress`` example uses the ``ip-permiss
 
     aws ec2 authorize-security-group-ingress \
         --group-id sg-1234567890abcdef0 \
-        --ip-permissions 'IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges=[{CidrIp=172.31.0.0/16}]" "IpProtocol=icmp,FromPort=-1,ToPort=-1,IpRanges=[{CidrIp=172.31.0.0/16}]'
+        --ip-permissions 'IpProtocol=tcp,FromPort=3389,ToPort=3389,IpRanges=[{CidrIp=172.31.0.0/16}]' 'IpProtocol=icmp,FromPort=-1,ToPort=-1,IpRanges=[{CidrIp=172.31.0.0/16}]'
 
 Output::
 

awscli/examples/ec2/create-ipam-resource-discovery.rst

@@ -43,4 +43,4 @@ Output::
             ]
     }
 
-Once you create a resource discovery, you may want to share it with another IPAM delegated admin, which you can do with `create-resource-share <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-resource-share.html>`__. For more information, see `Integrate IPAM with accounts outside of your organization <https://docs.aws.amazon.com/vpc/latest/ipam/enable-integ-ipam-outside-org.html>`__ in the *Amazon VPC IPAM User Guide*.
+Once you create a resource discovery, you may want to share it with another IPAM delegated admin, which you can do with `create-resource-share <https://docs.aws.amazon.com/cli/latest/reference/ram/create-resource-share.html>`__. For more information, see `Integrate IPAM with accounts outside of your organization <https://docs.aws.amazon.com/vpc/latest/ipam/enable-integ-ipam-outside-org.html>`__ in the *Amazon VPC IPAM User Guide*.

awscli/examples/ec2/delete-ipam-pool.rst

@@ -4,7 +4,7 @@ In this example, you're a IPAM delegated admin who wants to delete an IPAM pool
 
 To complete this request:
 
-* You'll need the IPAM pool ID which you can get with `describe-ipam-pools <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-pools.html>`__. 
+* You'll need the IPAM pool ID which you can get with `describe-ipam-pools <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-pools.html>`__. 
 * The ``--region`` must be the IPAM home Region.
 
 The following ``delete-ipam-pool`` example deletes an IPAM pool in your AWS account. ::

awscli/examples/ec2/describe-addresses-attribute.rst

@@ -26,4 +26,4 @@ Output::
         ]
     }
 
-To view the attributes of an elastic IP address, you must have first associated a domain name with the elastic IP address. For more information, see `Use reverse DNS for email applications <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#Using_Elastic_Addressing_Reverse_DNS>`__ in the *Amazon EC2 User Guide* or `modify-address-attribute <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/modify-address-attribute.html>`__ in the *AWS CLI Command Reference*.
+To view the attributes of an elastic IP address, you must have first associated a domain name with the elastic IP address. For more information, see `Use reverse DNS for email applications <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#Using_Elastic_Addressing_Reverse_DNS>`__ in the *Amazon EC2 User Guide* or `modify-address-attribute <https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-address-attribute.html>`__ in the *AWS CLI Command Reference*.

awscli/examples/ec2/get-ipam-discovered-public-addresses.rst

@@ -1,6 +1,6 @@
 **To view discovered public IP addresses**
 
-In this example, you are an IPAM delegated admin and you want to view the IP addresses of resources discovered by IPAM. You can get the resource discovery ID with `describe-ipam-resource-discoveries <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__.
+In this example, you are an IPAM delegated admin and you want to view the IP addresses of resources discovered by IPAM. You can get the resource discovery ID with `describe-ipam-resource-discoveries <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__.
 
 The following ``get-ipam-discovered-public-addresses`` example shows the discovered public IP addresses for a resource discovery. ::
 

awscli/examples/ec2/modify-ipam-resource-discovery.rst

@@ -5,7 +5,7 @@ In this example, you're an IPAM delegated admin who wants to modify the operatin
 To complete this request:
 
 * You cannot modify a default resource discovery and you must be the owner of the resource discovery.
-* You need the resource discovery ID, which you can get with `describe-ipam-resource-discoveries <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__.
+* You need the resource discovery ID, which you can get with `describe-ipam-resource-discoveries <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-resource-discoveries.html>`__.
 
 The following ``modify-ipam-resource-discovery`` example modifies a non-default resource discovery in your AWS account. ::
 

awscli/examples/ec2/modify-ipam-scope.rst

@@ -2,7 +2,7 @@
 
 In this scenario, you're an IPAM delegated admin who wants to modify the description of an IPAM scope. 
 
-To complete this request, you'll need the scope ID, which you can get with `describe-ipam-scopes <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-scopes.html>`__.
+To complete this request, you'll need the scope ID, which you can get with `describe-ipam-scopes <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-scopes.html>`__.
 
 The following ``modify-ipam-scope`` example updates the description of the scope. ::
 

awscli/examples/ec2/release-ipam-pool-allocation.rst

@@ -4,8 +4,8 @@ In this example, you're an IPAM delegated admin who tried to delete an IPAM pool
 
 Note the following:
 
-* You can only use this command for custom allocations. To remove an allocation for a resource without deleting the resource, set its monitored state to false using `modify-ipam-resource-cidr <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/modify-ipam-resource-cidr.html>`__.
-* To complete this request, you'll need the IPAM pool ID, which you can get with `describe-ipam-pools <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-ipam-pools.html>`__. You'll also need the allocation ID, which you can get with `get-ipam-pool-allocations <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/get-ipam-pool-allocations.html>`__.
+* You can only use this command for custom allocations. To remove an allocation for a resource without deleting the resource, set its monitored state to false using `modify-ipam-resource-cidr <https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-ipam-resource-cidr.html>`__.
+* To complete this request, you'll need the IPAM pool ID, which you can get with `describe-ipam-pools <https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipam-pools.html>`__. You'll also need the allocation ID, which you can get with `get-ipam-pool-allocations <https://docs.aws.amazon.com/cli/latest/reference/ec2/get-ipam-pool-allocations.html>`__.
 * If you do not want to remove allocations one by one, you can use the ``--cascade option`` when you delete an IPAM pool to automatically release any allocations in the pool before deleting it.
 * There are a number of prerequisites before running this command. For more information, see `Release an allocation <https://docs.aws.amazon.com/vpc/latest/ipam/release-alloc-ipam.html>`__ in the *Amazon VPC IPAM User Guide*.
 * The ``--region`` in which you run this command must be the locale of the IPAM pool where the allocation is.
@@ -24,4 +24,4 @@ Output::
         "Success": true
     }
 
-Once you release an allocation, you may want to run `delete-ipam-pool <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/delete-ipam-pool.html>`__.
+Once you release an allocation, you may want to run `delete-ipam-pool <https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-ipam-pool.html>`__.

awscli/examples/eks/associate-access-policy.rst

@@ -0,0 +1,29 @@
+**To associate an access policy and its scope to the access entry of the cluster**
+
+The following ``associate-access-policy`` associates an access policy and its scope to the access entry of the specified cluster. ::
+
+    aws eks associate-access-policy \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:role/Admin \
+        --policy-arn arn:aws:eks::aws:cluster-access-policy/AmazonEKSEditPolicy \
+        --access-scope type=namespace,namespaces=default
+
+Output::
+
+    {
+        "clusterName": "eks-customer",
+        "principalArn": "arn:aws:iam::111122223333:role/Admin",
+        "associatedAccessPolicy": {
+            "policyArn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSEditPolicy",
+            "accessScope": {
+                "type": "namespace",
+                "namespaces": [
+                    "default"
+                ]
+            },
+            "associatedAt": "2025-05-24T15:59:51.981000-05:00",
+            "modifiedAt": "2025-05-24T15:59:51.981000-05:00"
+        }
+    }
+
+For more information, see `Associate access policies with access entries <https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/create-access-entry.rst

@@ -0,0 +1,54 @@
+**Example 1: To create the access entry for EKS cluster**
+
+The following ``create-access-entry`` example creates an access entry that allows an IAM principal to access the EKS cluster. ::
+
+    aws eks create-access-entry \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:user/eks-user
+
+Output::
+
+    {
+        "accessEntry": {
+            "clusterName": "eks-customer",
+            "principalArn": "arn:aws:iam::111122223333:user/eks-user",
+            "kubernetesGroups": [],
+            "accessEntryArn": "arn:aws:eks:us-west-2:111122223333:access-entry/eks-customer/user/111122223333/eks-user/a1b2c3d4-5678-90ab-cdef-a6506e3d36p0",
+            "createdAt": "2025-04-14T22:45:48.097000-05:00",
+            "modifiedAt": "2025-04-14T22:45:48.097000-05:00",
+            "tags": {},
+            "username": "arn:aws:iam::111122223333:user/eks-user",
+            "type": "STANDARD"
+        }
+    }
+
+For more information, see `Create access entries <https://docs.aws.amazon.com/eks/latest/userguide/creating-access-entries.html>`__ in the *Amazon EKS User Guide*.
+
+**Example 2: To create the access entry for EKS cluster by specifying the type of access entry**
+
+The following ``create-access-entry`` example creates an access entry of type ``EC2_LINUX`` in the EKS cluster. By default, a type ``STANDARD`` access entry is created. Apart from the default, if we specify any other access entry types, an IAM role ARN needs to be passed in the CLI. ::
+
+    aws eks create-access-entry \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:role/admin-test-ip \
+        --type EC2_LINUX
+
+Output::
+
+    {
+        "accessEntry": {
+            "clusterName": "eks-customer",
+            "principalArn": "arn:aws:iam::111122223333:role/admin-test-ip",
+            "kubernetesGroups": [
+                "system:nodes"
+            ],
+            "accessEntryArn": "arn:aws:eks:us-west-2:111122223333:access-entry/eks-customer/role/111122223333/admin-test-ip/accb5418-f493-f390-3e6e-c3f19f725fcp",
+            "createdAt": "2025-05-06T19:42:45.453000-05:00",
+            "modifiedAt": "2025-05-06T19:42:45.453000-05:00",
+            "tags": {},
+            "username": "system:node:{{EC2PrivateDNSName}}",
+            "type": "EC2_LINUX"
+        }
+    }
+
+For more information, see `Create access entries <https://docs.aws.amazon.com/eks/latest/userguide/creating-access-entries.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/create-pod-identity-association.rst

@@ -0,0 +1,59 @@
+**Example 1: To create an EKS Pod Identity association in EKS cluster**
+
+The following ``create-pod-identity-association`` example creates an EKS Pod Identity association between a service account in the EKS cluster and an IAM role. ::
+
+    aws eks create-pod-identity-association \
+        --cluster-name eks-customer \
+        --namespace default \
+        --service-account default \
+        --role-arn arn:aws:iam::111122223333:role/my-role
+
+Output::
+
+    {
+        "association": {
+            "clusterName": "eks-customer",
+            "namespace": "default",
+            "serviceAccount": "default",
+            "roleArn": "arn:aws:iam::111122223333:role/my-role",
+            "associationArn": "arn:aws:eks:us-west-2:111122223333:podidentityassociation/eks-customer/a-8mvwvh57cu74mgcst",
+            "associationId": "a-8mvwvh57cu74mgcst",
+            "tags": {},
+            "createdAt": "2025-05-24T19:40:13.961000-05:00",
+            "modifiedAt": "2025-05-24T19:40:13.961000-05:00"
+        }
+    }
+
+For more information, see `Learn how EKS Pod Identity grants pods access to AWS services <https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html>`__ in the *Amazon EKS User Guide*.
+
+**Example 2: To create an EKS Pod Identity association in EKS cluster with tags**
+
+The following ``create-pod-identity-association`` creates an EKS Pod Identity association between a service account and an IAM role in the EKS cluster with tags. ::
+
+    aws eks create-pod-identity-association \
+        --cluster-name eks-customer \
+        --namespace default \
+        --service-account default \
+        --role-arn arn:aws:iam::111122223333:role/my-role \
+        --tags Key1=value1,Key2=value2
+
+Output::
+
+    {
+        "association": {
+            "clusterName": "eks-customer",
+            "namespace": "default",
+            "serviceAccount": "default",
+            "roleArn": "arn:aws:iam::111122223333:role/my-role",
+            "associationArn": "arn:aws:eks:us-west-2:111122223333:podidentityassociation/eks-customer/a-9njjin9gfghecgoda",
+            "associationId": "a-9njjin9gfghecgoda",
+            "tags": {
+                "Key2": "value2",
+                "Key1": "value1"
+            },
+            "createdAt": "2025-05-24T19:52:14.135000-05:00",
+            "modifiedAt": "2025-05-24T19:52:14.135000-05:00"
+        }
+    }
+
+For more information, see `Learn how EKS Pod Identity grants pods access to AWS services <https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/delete-access-entry.rst

@@ -0,0 +1,11 @@
+**To delete an access entry associated with the cluster**
+
+The following ``delete-access-entry`` deletes an access entry associated with the EKS cluster named ``eks-customer``. ::
+
+    aws eks delete-access-entry \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:role/Admin
+
+This command produces no output.
+
+For more information, see `Delete access entries <https://docs.aws.amazon.com/eks/latest/userguide/deleting-access-entries.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/delete-pod-identity-association.rst

@@ -0,0 +1,28 @@
+**To delete the EKS Pod Identity association**
+
+The following ``delete-pod-identity-association`` example deletes the EKS Pod Identity association with association ID ``a-9njjin9gfghecgocd`` from the EKS cluster named ``eks-customer``. ::
+
+    aws eks delete-pod-identity-association \
+        --cluster-name eks-customer \
+        --association-id a-9njjin9gfghecgocd
+
+Output::
+
+    {
+        "association": {
+            "clusterName": "eks-customer",
+            "namespace": "default",
+            "serviceAccount": "default",
+            "roleArn": "arn:aws:iam::111122223333:role/s3-role",
+            "associationArn": "arn:aws:eks:us-west-2:111122223333:podidentityassociation/eks-customer/a-9njjin9gfghecgocd",
+            "associationId": "a-9njjin9gfghecgocd",
+            "tags": {
+                "Key2": "value2",
+                "Key1": "value1"
+            },
+            "createdAt": "2025-05-24T19:52:14.135000-05:00",
+            "modifiedAt": "2025-05-25T21:10:56.923000-05:00"
+        }
+    }
+
+For more information, see `Learn how EKS Pod Identity grants pods access to AWS services <https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/describe-access-entry.rst

@@ -0,0 +1,25 @@
+**To describe the access entry for EKS cluster**
+
+The following ``describe-access-entry`` example describes an access entry for the EKS cluster. ::
+
+    aws eks describe-access-entry \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:user/eks-admin-user
+
+Output::
+
+    {
+        "accessEntry": {
+            "clusterName": "eks-customer",
+            "principalArn": "arn:aws:iam::111122223333:user/eks-admin-user",
+            "kubernetesGroups": [],
+            "accessEntryArn": "arn:aws:eks:us-west-2:111122223333:access-entry/eks-customer/user/111122223333/eks-admin-user/0acb1bc6-cb0a-ede6-11ae-a6506e3d36p0",
+            "createdAt": "2025-04-14T22:45:48.097000-05:00",
+            "modifiedAt": "2025-04-14T22:45:48.097000-05:00",
+            "tags": {},
+            "username": "arn:aws:iam::111122223333:user/eks-admin-user",
+            "type": "STANDARD"
+        }
+    }
+
+For more information, see `Grant IAM users access to Kubernetes with EKS access entries <https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/describe-insight.rst

@@ -0,0 +1,36 @@
+**To get the details of an insight for an EKS cluster using its ID**
+
+The following ``describe-insight`` example returns the details about the insight specified using the cluster name and insight ID. ::
+
+    aws eks describe-insight \
+        --cluster-name eks-customer \
+        --id 38ea7a64-a14f-4e0e-95c7-8dbcab3c3623
+
+Output::
+
+    {
+        "insight": {
+            "id": "38ea7a64-a14f-4e0e-95c7-8dbcab3c3623",
+            "name": "Kubelet version skew",
+            "category": "UPGRADE_READINESS",
+            "kubernetesVersion": "1.33",
+            "lastRefreshTime": "2025-05-24T11:22:50-05:00",
+            "lastTransitionTime": "2025-05-24T11:22:50-05:00",
+            "description": "Checks for kubelet versions of worker nodes in the cluster to see if upgrade would cause noncompliance with supported Kubernetes kubelet version skew policy.",
+            "insightStatus": {
+                "status": "PASSING",
+                "reason": "Node kubelet versions match the cluster control plane version."
+            },
+            "recommendation": "Upgrade your worker nodes to match the Kubernetes version of your cluster control plane.",
+            "additionalInfo": {
+                "Kubelet version skew policy": "https://kubernetes.io/releases/version-skew-policy/#kubelet",
+                "Updating a managed node group": "https://docs.aws.amazon.com/eks/latest/userguide/update-managed-node-group.html"
+            },
+            "resources": [],
+            "categorySpecificSummary": {
+                "deprecationDetails": []
+            }
+        }
+    }
+
+For more information, see `View cluster insights <https://docs.aws.amazon.com/eks/latest/userguide/view-cluster-insights.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/describe-pod-identity-association.rst

@@ -0,0 +1,28 @@
+**To provide the details about Pod Identity association**
+
+The following ``describe-pod-identity-association`` example describes a Pod Identity association in the EKS cluster. ::
+
+    aws eks describe-pod-identity-association \
+        --cluster-name eks-customer \
+        --association-id a-9njjin9gfghecgocd
+
+Output::
+
+    {
+        "association": {
+            "clusterName": "eks-customer",
+            "namespace": "default",
+            "serviceAccount": "default",
+            "roleArn": "arn:aws:iam::111122223333:role/my-role",
+            "associationArn": "arn:aws:eks:us-west-2:111122223333:podidentityassociation/eks-customer/a-9njjin9gfghecgocd",
+            "associationId": "a-9njjin9gfghecgocd",
+            "tags": {
+                "Key2": "value2",
+                "Key1": "value1"
+            },
+            "createdAt": "2025-05-24T19:52:14.135000-05:00",
+            "modifiedAt": "2025-05-24T19:52:14.135000-05:00"
+        }
+    }
+
+For more information, see `Learn how EKS Pod Identity grants pods access to AWS services <https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/disassociate-access-policy.rst

@@ -0,0 +1,12 @@
+**To disassociate the access policy from an access entry**
+
+The following ``disassociate-access-policy`` removes the access policy associated with the access entry. ::
+
+    aws eks disassociate-access-policy \
+        --cluster-name eks-customer \
+        --principal-arn arn:aws:iam::111122223333:role/Admin \
+        --policy-arn arn:aws:eks::aws:cluster-access-policy/AmazonEKSEditPolicy
+
+This command produces no output.
+
+For more information, see `Associate access policies with access entries <https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/list-access-entries.rst

@@ -0,0 +1,19 @@
+**To list the access entries for an EKS cluster**
+
+The following ``list-access-entries`` returns the list of access entries associated with the EKS cluster ``eks-customer``. ::
+
+    aws eks list-access-entries \
+        --cluster-name eks-customer
+
+Output::
+
+    {
+        "accessEntries": [
+            "arn:aws:iam::111122223333:role/Admin",
+            "arn:aws:iam::111122223333:role/admin-test-ip",
+            "arn:aws:iam::111122223333:role/assume-worker-node-role",
+            "arn:aws:iam::111122223333:user/eks-admin-user"
+        ]
+    }
+
+For more information, see `Grant IAM users access to Kubernetes with EKS access entries <https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html>`__ in the *Amazon EKS User Guide*.

awscli/examples/eks/list-access-policies.rst

@@ -0,0 +1,90 @@
+**To list all available access policies**
+
+This ``list-access-policies`` example returns the list of all available access policies. ::
+
+    aws eks list-access-policies
+
+Output::
+
+    {
+        "accessPolicies": [
+            {
+                "name": "AmazonEKSAdminPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSAdminPolicy"
+            },
+            {
+                "name": "AmazonEKSAdminViewPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSAdminViewPolicy"
+            },
+            {
+                "name": "AmazonEKSAutoNodePolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSAutoNodePolicy"
+            },
+            {
+                "name": "AmazonEKSBlockStorageClusterPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSBlockStorageClusterPolicy"
+            },
+            {
+                "name": "AmazonEKSBlockStoragePolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSBlockStoragePolicy"
+            },
+            {
+                "name": "AmazonEKSClusterAdminPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSClusterAdminPolicy"
+            },
+            {
+                "name": "AmazonEKSComputeClusterPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSComputeClusterPolicy"
+            },
+            {
+                "name": "AmazonEKSComputePolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSComputePolicy"
+            },
+            {
+                "name": "AmazonEKSEditPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSEditPolicy"
+            },
+            {
+                "name": "AmazonEKSHybridPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSHybridPolicy"
+            },
+            {
+                "name": "AmazonEKSLoadBalancingClusterPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSLoadBalancingClusterPolicy"
+            },
+            {
+                "name": "AmazonEKSLoadBalancingPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSLoadBalancingPolicy"
+            },
+            {
+                "name": "AmazonEKSNetworkingClusterPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSNetworkingClusterPolicy"
+            },
+            {
+                "name": "AmazonEKSNetworkingPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSNetworkingPolicy"
+            },
+            {
+                "name": "AmazonEKSViewPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEKSViewPolicy"
+            },
+            {
+                "name": "AmazonEMRJobPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonEMRJobPolicy"
+            },
+            {
+                "name": "AmazonSagemakerHyperpodClusterPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonSagemakerHyperpodClusterPolicy"
+            },
+            {
+                "name": "AmazonSagemakerHyperpodControllerPolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonSagemakerHyperpodControllerPolicy"
+            },
+            {
+                "name": "AmazonSagemakerHyperpodSystemNamespacePolicy",
+                "arn": "arn:aws:eks::aws:cluster-access-policy/AmazonSagemakerHyperpodSystemNamespacePolicy"
+            }
+        ]
+    }
+
+For more information, see `Associate access policies with access entries <https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html>`__ in the *Amazon EKS User Guide*.