@aws-sdk/client-eks 3.758.0 → 3.759.0

package/README.md

@@ -6,16 +6,16 @@
 
 AWS SDK for JavaScript EKS Client for Node.js, Browser and React Native.
 
-<p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
-for you to run Kubernetes on Amazon Web Services without needing to setup or maintain your own
-Kubernetes control plane. Kubernetes is an open-source system for automating the deployment,
-scaling, and management of containerized applications.</p>
-<p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you
-can use all the existing plugins and tooling from the Kubernetes community. Applications
-running on Amazon EKS are fully compatible with applications running on any
-standard Kubernetes environment, whether running in on-premises data centers or public
-clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS
-without any code modification required.</p>
+<p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on
+Amazon Web Services without needing to setup or maintain your own Kubernetes control plane. Kubernetes is an
+open-source system for automating the deployment, scaling, and management of
+containerized applications.</p>
+<p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all
+the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS
+are fully compatible with applications running on any standard Kubernetes environment,
+whether running in on-premises data centers or public clouds. This means that you can
+easily migrate any standard Kubernetes application to Amazon EKS without any code modification
+required.</p>
 
 ## Installing
 

package/dist-cjs/index.js

@@ -855,8 +855,8 @@ var UnsupportedAvailabilityZoneException = class _UnsupportedAvailabilityZoneExc
    */
   nodegroupName;
   /**
-   * <p>The supported Availability Zones for your account. Choose subnets in these
-   *             Availability Zones for your cluster.</p>
+   * <p>The supported Availability Zones for your account. Choose subnets in these Availability Zones for your
+   *             cluster.</p>
    * @public
    */
   validZones;
@@ -3125,6 +3125,7 @@ var de_EksAnywhereSubscription = /* @__PURE__ */ __name((output, context) => {
     licenseArns: import_smithy_client._json,
     licenseQuantity: import_smithy_client.expectInt32,
     licenseType: import_smithy_client.expectString,
+    licenses: import_smithy_client._json,
     status: import_smithy_client.expectString,
     tags: import_smithy_client._json,
     term: import_smithy_client._json

package/dist-es/protocols/Aws_restJson1.js

@@ -2037,6 +2037,7 @@ const de_EksAnywhereSubscription = (output, context) => {
         licenseArns: _json,
         licenseQuantity: __expectInt32,
         licenseType: __expectString,
+        licenses: _json,
         status: __expectString,
         tags: _json,
         term: _json,

package/dist-types/EKS.d.ts

@@ -407,16 +407,16 @@ export interface EKS {
     updatePodIdentityAssociation(args: UpdatePodIdentityAssociationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdatePodIdentityAssociationCommandOutput) => void): void;
 }
 /**
- * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
- *             for you to run Kubernetes on Amazon Web Services without needing to setup or maintain your own
- *             Kubernetes control plane. Kubernetes is an open-source system for automating the deployment,
- *             scaling, and management of containerized applications.</p>
- *          <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you
- *             can use all the existing plugins and tooling from the Kubernetes community. Applications
- *             running on Amazon EKS are fully compatible with applications running on any
- *             standard Kubernetes environment, whether running in on-premises data centers or public
- *             clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS
- *                  without any code modification required.</p>
+ * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on
+ *             Amazon Web Services without needing to setup or maintain your own Kubernetes control plane. Kubernetes is an
+ *             open-source system for automating the deployment, scaling, and management of
+ *             containerized applications.</p>
+ *          <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all
+ *             the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS
+ *             are fully compatible with applications running on any standard Kubernetes environment,
+ *             whether running in on-premises data centers or public clouds. This means that you can
+ *             easily migrate any standard Kubernetes application to Amazon EKS without any code modification
+ *             required.</p>
  * @public
  */
 export declare class EKS extends EKSClient implements EKS {

package/dist-types/EKSClient.d.ts

@@ -226,16 +226,16 @@ export type EKSClientResolvedConfigType = __SmithyResolvedConfiguration<__HttpHa
 export interface EKSClientResolvedConfig extends EKSClientResolvedConfigType {
 }
 /**
- * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
- *             for you to run Kubernetes on Amazon Web Services without needing to setup or maintain your own
- *             Kubernetes control plane. Kubernetes is an open-source system for automating the deployment,
- *             scaling, and management of containerized applications.</p>
- *          <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you
- *             can use all the existing plugins and tooling from the Kubernetes community. Applications
- *             running on Amazon EKS are fully compatible with applications running on any
- *             standard Kubernetes environment, whether running in on-premises data centers or public
- *             clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS
- *                  without any code modification required.</p>
+ * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on
+ *             Amazon Web Services without needing to setup or maintain your own Kubernetes control plane. Kubernetes is an
+ *             open-source system for automating the deployment, scaling, and management of
+ *             containerized applications.</p>
+ *          <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all
+ *             the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS
+ *             are fully compatible with applications running on any standard Kubernetes environment,
+ *             whether running in on-premises data centers or public clouds. This means that you can
+ *             easily migrate any standard Kubernetes application to Amazon EKS without any code modification
+ *             required.</p>
  * @public
  */
 export declare class EKSClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, EKSClientResolvedConfig> {

package/dist-types/commands/AssociateAccessPolicyCommand.d.ts

@@ -85,7 +85,7 @@ declare const AssociateAccessPolicyCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/AssociateEncryptionConfigCommand.d.ts

@@ -105,7 +105,7 @@ declare const AssociateEncryptionConfigCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/AssociateIdentityProviderConfigCommand.d.ts

@@ -117,7 +117,7 @@ declare const AssociateIdentityProviderConfigCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/CreateAccessEntryCommand.d.ts

@@ -32,11 +32,11 @@ declare const CreateAccessEntryCommand_base: {
  *             entries can replace the need to maintain entries in the <code>aws-auth</code>
  *             <code>ConfigMap</code> for authentication. You have the following options for
  *             authorizing an IAM principal to access Kubernetes objects on your cluster: Kubernetes
- *             role-based access control (RBAC), Amazon EKS, or both. Kubernetes RBAC authorization
- *             requires you to create and manage Kubernetes <code>Role</code>, <code>ClusterRole</code>,
+ *             role-based access control (RBAC), Amazon EKS, or both. Kubernetes RBAC authorization requires you
+ *             to create and manage Kubernetes <code>Role</code>, <code>ClusterRole</code>,
  *                 <code>RoleBinding</code>, and <code>ClusterRoleBinding</code> objects, in addition
- *             to managing access entries. If you use Amazon EKS authorization exclusively, you
- *             don't need to create and manage Kubernetes <code>Role</code>, <code>ClusterRole</code>,
+ *             to managing access entries. If you use Amazon EKS authorization exclusively, you don't need
+ *             to create and manage Kubernetes <code>Role</code>, <code>ClusterRole</code>,
  *                 <code>RoleBinding</code>, and <code>ClusterRoleBinding</code> objects.</p>
  *          <p>For more information about access entries, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html">Access entries</a> in the
  *             <i>Amazon EKS User Guide</i>.</p>
@@ -105,7 +105,7 @@ declare const CreateAccessEntryCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/CreateAddonCommand.d.ts

@@ -28,10 +28,9 @@ declare const CreateAddonCommand_base: {
 };
 /**
  * <p>Creates an Amazon EKS add-on.</p>
- *          <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management
- *             of common operational software for Amazon EKS clusters. For more information,
- *             see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html">Amazon EKS
- *                      add-ons</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *          <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management of common
+ *             operational software for Amazon EKS clusters. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html">Amazon EKS
+ *                 add-ons</a> in the <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -123,7 +122,7 @@ declare const CreateAddonCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/CreateClusterCommand.d.ts

@@ -28,45 +28,42 @@ declare const CreateClusterCommand_base: {
 };
 /**
  * <p>Creates an Amazon EKS control plane.</p>
- *          <p>The Amazon EKS control plane consists of control plane instances that run the
- *             Kubernetes software, such as <code>etcd</code> and the API server. The control plane runs in
- *             an account managed by Amazon Web Services, and the Kubernetes API is exposed by the Amazon EKS
- *                  API server endpoint. Each Amazon EKS cluster control plane is
- *             single tenant and unique. It runs on its own set of Amazon EC2 instances.</p>
- *          <p>The cluster control plane is provisioned across multiple Availability Zones and
- *             fronted by an Elastic Load Balancing
- *             Network Load Balancer. Amazon EKS also provisions elastic network interfaces in
- *             your VPC subnets to provide connectivity from the control plane instances to the nodes
- *             (for example, to support <code>kubectl exec</code>, <code>logs</code>, and
- *                 <code>proxy</code> data flows).</p>
- *          <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your
- *             cluster's control plane over the Kubernetes API server endpoint and a certificate file that
- *             is created for your cluster.</p>
+ *          <p>The Amazon EKS control plane consists of control plane instances that run the Kubernetes
+ *             software, such as <code>etcd</code> and the API server. The control plane runs in an
+ *             account managed by Amazon Web Services, and the Kubernetes API is exposed by the Amazon EKS API server endpoint.
+ *             Each Amazon EKS cluster control plane is single tenant and unique. It runs on its own set of
+ *             Amazon EC2 instances.</p>
+ *          <p>The cluster control plane is provisioned across multiple Availability Zones and fronted by an Elastic Load Balancing
+ *             Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC subnets to provide
+ *             connectivity from the control plane instances to the nodes (for example, to support
+ *                 <code>kubectl exec</code>, <code>logs</code>, and <code>proxy</code> data
+ *             flows).</p>
+ *          <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your cluster's control plane over
+ *             the Kubernetes API server endpoint and a certificate file that is created for your
+ *             cluster.</p>
  *          <p>You can use the <code>endpointPublicAccess</code> and
  *                 <code>endpointPrivateAccess</code> parameters to enable or disable public and
  *             private access to your cluster's Kubernetes API server endpoint. By default, public access is
- *             enabled, and private access is disabled. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html">Amazon EKS
- *                      Cluster Endpoint Access Control</a> in the
- *                 <i>
+ *             enabled, and private access is disabled. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html">Amazon EKS Cluster
+ *                 Endpoint Access Control</a> in the <i>
  *                <i>Amazon EKS User Guide</i>
  *             </i>. </p>
  *          <p>You can use the <code>logging</code> parameter to enable or disable exporting the
- *             Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster
- *             control plane logs aren't exported to CloudWatch Logs. For more information, see
- *                 <a href="https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html">Amazon EKS Cluster Control Plane Logs</a> in the
- *                 <i>
+ *             Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster control plane
+ *             logs aren't exported to CloudWatch Logs. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html">Amazon EKS
+ *                 Cluster Control Plane Logs</a> in the
+ *             <i>
  *                <i>Amazon EKS User Guide</i>
  *             </i>.</p>
  *          <note>
- *             <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to
- *                 exported control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch
- *                 Pricing</a>.</p>
+ *             <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported
+ *                 control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch Pricing</a>.</p>
  *          </note>
- *          <p>In most cases, it takes several minutes to create a cluster. After you create an
- *                 Amazon EKS cluster, you must configure your Kubernetes tooling to communicate
- *             with the API server and launch nodes into your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-auth.html">Allowing users to
- *                 access your cluster</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching
- *                     Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *          <p>In most cases, it takes several minutes to create a cluster. After you create an Amazon EKS
+ *             cluster, you must configure your Kubernetes tooling to communicate with the API server and
+ *             launch nodes into your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-auth.html">Allowing users to
+ *                 access your cluster</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching Amazon EKS
+ *                 nodes</a> in the <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -320,10 +317,9 @@ declare const CreateClusterCommand_base: {
  *  <p>The service is unavailable. Back off and retry the operation.</p>
  *
  * @throws {@link UnsupportedAvailabilityZoneException} (client fault)
- *  <p>At least one of your specified cluster subnets is in an Availability Zone that does
- *             not support Amazon EKS. The exception output specifies the supported
- *             Availability Zones for your account, from which you can choose subnets for your
- *             cluster.</p>
+ *  <p>At least one of your specified cluster subnets is in an Availability Zone that does not support
+ *             Amazon EKS. The exception output specifies the supported Availability Zones for your account, from which
+ *             you can choose subnets for your cluster.</p>
  *
  * @throws {@link EKSServiceException}
  * <p>Base exception class for all service exceptions from EKS service.</p>

package/dist-types/commands/CreateEksAnywhereSubscriptionCommand.d.ts

@@ -71,6 +71,12 @@ declare const CreateEksAnywhereSubscriptionCommand_base: {
  * //     licenseArns: [ // StringList
  * //       "STRING_VALUE",
  * //     ],
+ * //     licenses: [ // LicenseList
+ * //       { // License
+ * //         id: "STRING_VALUE",
+ * //         token: "STRING_VALUE",
+ * //       },
+ * //     ],
  * //     tags: { // TagMap
  * //       "<keys>": "STRING_VALUE",
  * //     },

package/dist-types/commands/CreateFargateProfileCommand.d.ts

@@ -27,34 +27,31 @@ declare const CreateFargateProfileCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates an Fargate profile for your Amazon EKS cluster. You
- *             must have at least one Fargate profile in a cluster to be able to run
- *             pods on Fargate.</p>
- *          <p>The Fargate profile allows an administrator to declare which pods run
- *             on Fargate and specify which pods run on which Fargate
- *             profile. This declaration is done through the profile's selectors. Each profile can have
- *             up to five selectors that contain a namespace and labels. A namespace is required for
- *             every selector. The label field consists of multiple optional key-value pairs. Pods that
- *             match the selectors are scheduled on Fargate. If a to-be-scheduled pod
- *             matches any of the selectors in the Fargate profile, then that pod is run
- *             on Fargate.</p>
- *          <p>When you create a Fargate profile, you must specify a pod execution
- *             role to use with the pods that are scheduled with the profile. This role is added to the
- *             cluster's Kubernetes <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/">Role Based
- *                 Access Control</a> (RBAC) for authorization so that the <code>kubelet</code>
- *             that is running on the Fargate infrastructure can register with your
- *                 Amazon EKS cluster so that it can appear in your cluster as a node. The pod
- *             execution role also provides IAM permissions to the Fargate infrastructure to
- *             allow read access to Amazon ECR image repositories. For
- *             more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
- *          <p>Fargate profiles are immutable. However, you can create a new updated
- *             profile to replace an existing profile and then delete the original after the updated
- *             profile has finished creating.</p>
- *          <p>If any Fargate profiles in a cluster are in the <code>DELETING</code>
- *             status, you must wait for that Fargate profile to finish deleting before
- *             you can create any other profiles in that cluster.</p>
- *          <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate profile</a> in the
- *             <i>Amazon EKS User Guide</i>.</p>
+ * <p>Creates an Fargate profile for your Amazon EKS cluster. You must have at least one
+ *             Fargate profile in a cluster to be able to run pods on Fargate.</p>
+ *          <p>The Fargate profile allows an administrator to declare which pods run on Fargate
+ *             and specify which pods run on which Fargate profile. This declaration is done through
+ *             the profile's selectors. Each profile can have up to five selectors that contain a
+ *             namespace and labels. A namespace is required for every selector. The label field
+ *             consists of multiple optional key-value pairs. Pods that match the selectors are
+ *             scheduled on Fargate. If a to-be-scheduled pod matches any of the selectors in the
+ *             Fargate profile, then that pod is run on Fargate.</p>
+ *          <p>When you create a Fargate profile, you must specify a pod execution role to use with
+ *             the pods that are scheduled with the profile. This role is added to the cluster's Kubernetes
+ *                 <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/">Role
+ *                 Based Access Control</a> (RBAC) for authorization so that the
+ *                 <code>kubelet</code> that is running on the Fargate infrastructure can register
+ *             with your Amazon EKS cluster so that it can appear in your cluster as a node. The pod
+ *             execution role also provides IAM permissions to the Fargate infrastructure to allow
+ *             read access to Amazon ECR image repositories. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod
+ *                 Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *          <p>Fargate profiles are immutable. However, you can create a new updated profile to
+ *             replace an existing profile and then delete the original after the updated profile has
+ *             finished creating.</p>
+ *          <p>If any Fargate profiles in a cluster are in the <code>DELETING</code> status, you
+ *             must wait for that Fargate profile to finish deleting before you can create any other
+ *             profiles in that cluster.</p>
+ *          <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate profile</a> in the <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -147,10 +144,9 @@ declare const CreateFargateProfileCommand_base: {
  *  <p>These errors are usually caused by a server-side issue.</p>
  *
  * @throws {@link UnsupportedAvailabilityZoneException} (client fault)
- *  <p>At least one of your specified cluster subnets is in an Availability Zone that does
- *             not support Amazon EKS. The exception output specifies the supported
- *             Availability Zones for your account, from which you can choose subnets for your
- *             cluster.</p>
+ *  <p>At least one of your specified cluster subnets is in an Availability Zone that does not support
+ *             Amazon EKS. The exception output specifies the supported Availability Zones for your account, from which
+ *             you can choose subnets for your cluster.</p>
  *
  * @throws {@link EKSServiceException}
  * <p>Base exception class for all service exceptions from EKS service.</p>

package/dist-types/commands/CreateNodegroupCommand.d.ts

@@ -31,14 +31,19 @@ declare const CreateNodegroupCommand_base: {
  *          <p>You can only create a node group for your cluster that is equal to the current Kubernetes
  *             version for the cluster. All node groups are created with the latest AMI release version
  *             for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI
- *             using a launch template. For more information about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Customizing managed nodes with launch templates</a>.</p>
- *          <p>An Amazon EKS managed node group is an Amazon EC2
- *             Auto Scaling group and associated Amazon EC2 instances that are managed by
- *                 Amazon Web Services for an Amazon EKS cluster. For more information, see
- *                 <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed node groups</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *             using a launch template.</p>
+ *          <p>For later updates, you will only be able to update a node group using a launch
+ *             template only if it was originally deployed with a launch template. Additionally, the
+ *             launch template ID or name must match what was used when the node group was created. You
+ *             can update the launch template version with necessary changes. For more information
+ *             about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Customizing managed nodes with
+ *                 launch templates</a>.</p>
+ *          <p>An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that
+ *             are managed by Amazon Web Services for an Amazon EKS cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed
+ *                 node groups</a> in the <i>Amazon EKS User Guide</i>.</p>
  *          <note>
- *             <p>Windows AMI types are only supported for commercial Amazon Web Services Regions
- *                 that support Windows on Amazon EKS.</p>
+ *             <p>Windows AMI types are only supported for commercial Amazon Web Services Regions that support
+ *                 Windows on Amazon EKS.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

package/dist-types/commands/CreatePodIdentityAssociationCommand.d.ts

@@ -99,7 +99,7 @@ declare const CreatePodIdentityAssociationCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteAccessEntryCommand.d.ts

@@ -61,7 +61,7 @@ declare const DeleteAccessEntryCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteAddonCommand.d.ts

@@ -105,7 +105,7 @@ declare const DeleteAddonCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteClusterCommand.d.ts

@@ -33,9 +33,9 @@ declare const DeleteClusterCommand_base: {
  *             are deleted properly. Otherwise, you can have orphaned resources in your VPC that
  *             prevent you from being able to delete the VPC. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/delete-cluster.html">Deleting a
  *                 cluster</a> in the <i>Amazon EKS User Guide</i>.</p>
- *          <p>If you have managed node groups or Fargate profiles attached to the
- *             cluster, you must delete them first. For more information, see
- *                 <code>DeleteNodgroup</code> and <code>DeleteFargateProfile</code>.</p>
+ *          <p>If you have managed node groups or Fargate profiles attached to the cluster, you
+ *             must delete them first. For more information, see <code>DeleteNodgroup</code> and
+ *                 <code>DeleteFargateProfile</code>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -191,7 +191,7 @@ declare const DeleteClusterCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteEksAnywhereSubscriptionCommand.d.ts

@@ -28,9 +28,9 @@ declare const DeleteEksAnywhereSubscriptionCommand_base: {
 };
 /**
  * <p>Deletes an expired or inactive subscription. Deleting inactive subscriptions removes
- *             them from the Amazon Web Services Management Console view and from list/describe API responses.
- *             Subscriptions can only be cancelled within 7 days of creation and are cancelled by
- *             creating a ticket in the Amazon Web Services Support Center. </p>
+ *             them from the Amazon Web Services Management Console view and from list/describe API responses. Subscriptions can
+ *             only be cancelled within 7 days of creation and are cancelled by creating a ticket in
+ *             the Amazon Web Services Support Center. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -60,6 +60,12 @@ declare const DeleteEksAnywhereSubscriptionCommand_base: {
  * //     licenseArns: [ // StringList
  * //       "STRING_VALUE",
  * //     ],
+ * //     licenses: [ // LicenseList
+ * //       { // License
+ * //         id: "STRING_VALUE",
+ * //         token: "STRING_VALUE",
+ * //       },
+ * //     ],
  * //     tags: { // TagMap
  * //       "<keys>": "STRING_VALUE",
  * //     },
@@ -87,7 +93,7 @@ declare const DeleteEksAnywhereSubscriptionCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteFargateProfileCommand.d.ts

@@ -28,16 +28,14 @@ declare const DeleteFargateProfileCommand_base: {
 };
 /**
  * <p>Deletes an Fargate profile.</p>
- *          <p>When you delete a Fargate profile, any <code>Pod</code> running on
- *                 Fargate that was created with the profile is deleted. If the
- *                 <code>Pod</code> matches another Fargate profile, then it is
- *             scheduled on Fargate with that profile. If it no longer matches any
- *                 Fargate profiles, then it's not scheduled on Fargate
- *             and may remain in a pending state.</p>
- *          <p>Only one Fargate profile in a cluster can be in the
- *                 <code>DELETING</code> status at a time. You must wait for a Fargate
- *             profile to finish deleting before you can delete any other profiles in that
- *             cluster.</p>
+ *          <p>When you delete a Fargate profile, any <code>Pod</code> running on Fargate that
+ *             was created with the profile is deleted. If the <code>Pod</code> matches another
+ *             Fargate profile, then it is scheduled on Fargate with that profile. If it no longer
+ *             matches any Fargate profiles, then it's not scheduled on Fargate and may remain in a
+ *             pending state.</p>
+ *          <p>Only one Fargate profile in a cluster can be in the <code>DELETING</code> status at
+ *             a time. You must wait for a Fargate profile to finish deleting before you can delete
+ *             any other profiles in that cluster.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -107,7 +105,7 @@ declare const DeleteFargateProfileCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeleteNodegroupCommand.d.ts

@@ -141,7 +141,7 @@ declare const DeleteNodegroupCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeletePodIdentityAssociationCommand.d.ts

@@ -78,7 +78,7 @@ declare const DeletePodIdentityAssociationCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>

package/dist-types/commands/DeregisterClusterCommand.d.ts

@@ -27,8 +27,7 @@ declare const DeregisterClusterCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Deregisters a connected cluster to remove it from the Amazon EKS control
- *             plane.</p>
+ * <p>Deregisters a connected cluster to remove it from the Amazon EKS control plane.</p>
  *          <p>A connected cluster is a Kubernetes cluster that you've connected to your control plane
  *             using the <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-connector.html">Amazon EKS Connector</a>.</p>
  * @example
@@ -176,10 +175,9 @@ declare const DeregisterClusterCommand_base: {
  *
  * @throws {@link AccessDeniedException} (client fault)
  *  <p>You don't have permissions to perform the requested operation. The <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html">IAM principal</a>
- *             making the request must have at least one IAM permissions policy attached
- *             that grants the required permissions. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html">Access
- *                 management</a> in the <i>IAM User Guide</i>.
- *         </p>
+ *             making the request must have at least one IAM permissions policy attached that grants
+ *             the required permissions. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html">Access
+ *                 management</a> in the <i>IAM User Guide</i>. </p>
  *
  * @throws {@link ClientException} (client fault)
  *  <p>These errors are usually caused by a client action. Actions can include using an
@@ -193,7 +191,7 @@ declare const DeregisterClusterCommand_base: {
  *  <p>The specified resource could not be found. You can view your available clusters with
  *                 <code>ListClusters</code>. You can view your available managed node groups with
  *                 <code>ListNodegroups</code>. Amazon EKS clusters and node groups are Amazon Web Services Region
- *                  specific.</p>
+ *             specific.</p>
  *
  * @throws {@link ServerException} (server fault)
  *  <p>These errors are usually caused by a server-side issue.</p>