@aws-sdk/client-eks 3.229.0 → 3.232.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (22) hide show
  1. package/dist-cjs/models/models_0.js +4 -0
  2. package/dist-es/models/models_0.js +4 -0
  3. package/dist-types/EKS.d.ts +52 -49
  4. package/dist-types/EKSClient.d.ts +1 -1
  5. package/dist-types/commands/AssociateEncryptionConfigCommand.d.ts +1 -1
  6. package/dist-types/commands/AssociateIdentityProviderConfigCommand.d.ts +1 -1
  7. package/dist-types/commands/CreateAddonCommand.d.ts +1 -1
  8. package/dist-types/commands/CreateClusterCommand.d.ts +4 -5
  9. package/dist-types/commands/CreateFargateProfileCommand.d.ts +5 -5
  10. package/dist-types/commands/CreateNodegroupCommand.d.ts +7 -4
  11. package/dist-types/commands/DeleteAddonCommand.d.ts +1 -1
  12. package/dist-types/commands/DeleteClusterCommand.d.ts +2 -2
  13. package/dist-types/commands/DeleteFargateProfileCommand.d.ts +2 -2
  14. package/dist-types/commands/DescribeClusterCommand.d.ts +3 -3
  15. package/dist-types/commands/DescribeUpdateCommand.d.ts +1 -1
  16. package/dist-types/commands/RegisterClusterCommand.d.ts +4 -5
  17. package/dist-types/commands/UpdateClusterConfigCommand.d.ts +7 -7
  18. package/dist-types/commands/UpdateClusterVersionCommand.d.ts +2 -2
  19. package/dist-types/commands/UpdateNodegroupVersionCommand.d.ts +10 -8
  20. package/dist-types/models/models_0.d.ts +136 -120
  21. package/dist-types/ts3.4/models/models_0.d.ts +4 -0
  22. package/package.json +5 -5
package/dist-types/models/models_0.d.ts CHANGED
@@ -95,7 +95,7 @@ export interface Addon {
95
95
  */
96
96
  addonVersion?: string;
97
97
  /**
98
- * <p>An object representing the health of the add-on.</p>
98
+ * <p>An object that represents the health of the add-on.</p>
99
99
  */
100
100
  health?: AddonHealth;
101
101
  /**
@@ -111,8 +111,8 @@ export interface Addon {
111
111
  */
112
112
  modifiedAt?: Date;
113
113
  /**
114
- * <p>The Amazon Resource Name (ARN) of the IAM role that is bound to the Kubernetes service
115
- * account used by the add-on.</p>
114
+ * <p>The Amazon Resource Name (ARN) of the IAM role that's bound to the Kubernetes service account
115
+ * that the add-on uses.</p>
116
116
  */
117
117
  serviceAccountRoleArn?: string;
118
118
  /**
@@ -134,7 +134,7 @@ export interface Addon {
134
134
  */
135
135
  marketplaceInformation?: MarketplaceInformation;
136
136
  /**
137
- * <p>The provided configuration values.</p>
137
+ * <p>The configuration values that you provided.</p>
138
138
  */
139
139
  configurationValues?: string;
140
140
  }
@@ -214,7 +214,11 @@ export declare enum AMITypes {
214
214
  BOTTLEROCKET_ARM_64_NVIDIA = "BOTTLEROCKET_ARM_64_NVIDIA",
215
215
  BOTTLEROCKET_x86_64 = "BOTTLEROCKET_x86_64",
216
216
  BOTTLEROCKET_x86_64_NVIDIA = "BOTTLEROCKET_x86_64_NVIDIA",
217
- CUSTOM = "CUSTOM"
217
+ CUSTOM = "CUSTOM",
218
+ WINDOWS_CORE_2019_x86_64 = "WINDOWS_CORE_2019_x86_64",
219
+ WINDOWS_CORE_2022_x86_64 = "WINDOWS_CORE_2022_x86_64",
220
+ WINDOWS_FULL_2019_x86_64 = "WINDOWS_FULL_2019_x86_64",
221
+ WINDOWS_FULL_2022_x86_64 = "WINDOWS_FULL_2022_x86_64"
218
222
  }
219
223
  /**
220
224
  * <p>Identifies the Key Management Service (KMS) key used to encrypt the
@@ -282,40 +286,40 @@ export declare enum ErrorCode {
282
286
  export interface ErrorDetail {
283
287
  /**
284
288
  * <p>A brief description of the error. </p>
285
- * <ul>
289
+ * <ul>
286
290
  * <li>
287
- * <p>
291
+ * <p>
288
292
  * <b>SubnetNotFound</b>: We couldn't find one of the
289
293
  * subnets associated with the cluster.</p>
290
294
  * </li>
291
295
  * <li>
292
- * <p>
296
+ * <p>
293
297
  * <b>SecurityGroupNotFound</b>: We couldn't find one
294
298
  * of the security groups associated with the cluster.</p>
295
299
  * </li>
296
300
  * <li>
297
- * <p>
301
+ * <p>
298
302
  * <b>EniLimitReached</b>: You have reached the elastic
299
303
  * network interface limit for your account.</p>
300
304
  * </li>
301
305
  * <li>
302
- * <p>
306
+ * <p>
303
307
  * <b>IpNotAvailable</b>: A subnet associated with the
304
308
  * cluster doesn't have any free IP addresses.</p>
305
309
  * </li>
306
310
  * <li>
307
- * <p>
311
+ * <p>
308
312
  * <b>AccessDenied</b>: You don't have permissions to
309
313
  * perform the specified operation.</p>
310
314
  * </li>
311
315
  * <li>
312
- * <p>
316
+ * <p>
313
317
  * <b>OperationNotPermitted</b>: The service role
314
318
  * associated with the cluster doesn't have the required access permissions for
315
319
  * Amazon EKS.</p>
316
320
  * </li>
317
321
  * <li>
318
- * <p>
322
+ * <p>
319
323
  * <b>VpcIdNotFound</b>: We couldn't find the VPC
320
324
  * associated with the cluster.</p>
321
325
  * </li>
@@ -669,9 +673,9 @@ export interface CreateAddonRequest {
669
673
  */
670
674
  clusterName: string | undefined;
671
675
  /**
672
- * <p>The name of the add-on. The name must match one of the names returned by <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonVersions.html">
676
+ * <p>The name of the add-on. The name must match one of the names that <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonVersions.html">
673
677
  * <code>DescribeAddonVersions</code>
674
- * </a>.</p>
678
+ * </a> returns.</p>
675
679
  */
676
680
  addonName: string | undefined;
677
681
  /**
@@ -683,7 +687,7 @@ export interface CreateAddonRequest {
683
687
  /**
684
688
  * <p>The Amazon Resource Name (ARN) of an existing IAM role to bind to the add-on's service account. The role must be assigned the IAM permissions required by the add-on. If you don't specify an existing IAM role, then the add-on uses the
685
689
  * permissions assigned to the node IAM role. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html">Amazon EKS node IAM role</a> in the <i>Amazon EKS User Guide</i>.</p>
686
- * <note>
690
+ * <note>
687
691
  * <p>To specify an existing IAM role, you must have an IAM OpenID Connect (OIDC) provider created for
688
692
  * your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html">Enabling
689
693
  * IAM roles for service accounts on your cluster</a> in the
@@ -694,27 +698,27 @@ export interface CreateAddonRequest {
694
698
  /**
695
699
  * <p>How to resolve field value conflicts for an Amazon EKS add-on. Conflicts are
696
700
  * handled based on the value you choose:</p>
697
- * <ul>
701
+ * <ul>
698
702
  * <li>
699
- * <p>
703
+ * <p>
700
704
  * <b>None</b> – If the self-managed version of
701
705
  * the add-on is installed on your cluster, Amazon EKS doesn't change the
702
706
  * value. Creation of the add-on might fail.</p>
703
707
  * </li>
704
708
  * <li>
705
- * <p>
709
+ * <p>
706
710
  * <b>Overwrite</b> – If the self-managed
707
711
  * version of the add-on is installed on your cluster and the Amazon EKS
708
712
  * default value is different than the existing value, Amazon EKS changes
709
713
  * the value to the Amazon EKS default value.</p>
710
714
  * </li>
711
715
  * <li>
712
- * <p>
716
+ * <p>
713
717
  * <b>Preserve</b> – Not supported. You can set
714
718
  * this value when updating an add-on though. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateAddon.html">UpdateAddon</a>.</p>
715
719
  * </li>
716
720
  * </ul>
717
- * <p>If you don't currently have the self-managed version of the add-on installed on your
721
+ * <p>If you don't currently have the self-managed version of the add-on installed on your
718
722
  * cluster, the Amazon EKS add-on is installed. Amazon EKS sets all values
719
723
  * to default values, regardless of the option that you specify.</p>
720
724
  */
@@ -730,8 +734,8 @@ export interface CreateAddonRequest {
730
734
  */
731
735
  tags?: Record<string, string>;
732
736
  /**
733
- * <p> The set of configuration values for the add-on being created. Whatever values
734
- * provided here are validated against the schema from <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonConfiguration.html">
737
+ * <p>The set of configuration values for the add-on that's created. The values that you
738
+ * provide are validated against the schema in <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonConfiguration.html">
735
739
  * <code>DescribeAddonConfiguration</code>
736
740
  * </a>.</p>
737
741
  */
@@ -758,23 +762,23 @@ export interface KubernetesNetworkConfigRequest {
758
762
  * or <code>172.20.0.0/16</code> CIDR blocks. We recommend that you specify a block that does not
759
763
  * overlap with resources in other networks that are peered or connected to your VPC. The
760
764
  * block must meet the following requirements:</p>
761
- * <ul>
765
+ * <ul>
762
766
  * <li>
763
- * <p>Within one of the following private IP address blocks: <code>10.0.0.0/8</code>,
767
+ * <p>Within one of the following private IP address blocks: <code>10.0.0.0/8</code>,
764
768
  * <code>172.16.0.0/12</code>, or <code>192.168.0.0/16</code>.</p>
765
769
  * </li>
766
770
  * <li>
767
- * <p>Doesn't overlap with any CIDR block assigned to the VPC that you selected for
771
+ * <p>Doesn't overlap with any CIDR block assigned to the VPC that you selected for
768
772
  * VPC.</p>
769
773
  * </li>
770
774
  * <li>
771
- * <p>Between /24 and /12.</p>
775
+ * <p>Between /24 and /12.</p>
772
776
  * </li>
773
777
  * </ul>
774
- * <important>
778
+ * <important>
775
779
  * <p>You can only specify a custom CIDR block when you create a cluster and can't
776
780
  * change this value once the cluster is created.</p>
777
- * </important>
781
+ * </important>
778
782
  */
779
783
  serviceIpv4Cidr?: string;
780
784
  /**
@@ -784,7 +788,7 @@ export interface KubernetesNetworkConfigRequest {
784
788
  * created. If you specify <code>ipv6</code>, the VPC and subnets that you specify for
785
789
  * cluster creation must have both <code>IPv4</code> and <code>IPv6</code> CIDR blocks assigned to them. You can't
786
790
  * specify <code>ipv6</code> for clusters in China Regions.</p>
787
- * <p>You can only specify <code>ipv6</code> for <code>1.21</code> and later clusters that use version
791
+ * <p>You can only specify <code>ipv6</code> for <code>1.21</code> and later clusters that use version
788
792
  * <code>1.10.1</code> or later of the Amazon VPC CNI add-on. If you specify <code>ipv6</code>, then ensure
789
793
  * that your VPC meets the requirements listed in the considerations listed in <a href="https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.html">Assigning IPv6
790
794
  * addresses to pods and services</a> in the Amazon EKS User Guide.
@@ -854,10 +858,10 @@ export interface OutpostConfigRequest {
854
858
  * <p>The Amazon EC2 instance type that you want to use for your local Amazon EKS cluster on Outposts. Choose an instance type based on the number of nodes
855
859
  * that your cluster will have. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts-capacity-considerations.html">Capacity
856
860
  * considerations</a> in the <i>Amazon EKS User Guide</i>.</p>
857
- * <p>The instance type that you specify is used for all Kubernetes control plane instances. The
861
+ * <p>The instance type that you specify is used for all Kubernetes control plane instances. The
858
862
  * instance type can't be changed after cluster creation. The control plane is not
859
863
  * automatically scaled by Amazon EKS.</p>
860
- * <p> </p>
864
+ * <p> </p>
861
865
  */
862
866
  controlPlaneInstanceType: string | undefined;
863
867
  /**
@@ -935,9 +939,9 @@ export interface CreateClusterRequest {
935
939
  /**
936
940
  * <p>The desired Kubernetes version for your cluster. If you don't specify a value here,
937
941
  * the default version available in Amazon EKS is used.</p>
938
- * <note>
942
+ * <note>
939
943
  * <p>The default version might not be the latest version available.</p>
940
- * </note>
944
+ * </note>
941
945
  */
942
946
  version?: string;
943
947
  /**
@@ -968,11 +972,11 @@ export interface CreateClusterRequest {
968
972
  * <i>
969
973
  * <i>Amazon EKS User Guide</i>
970
974
  * </i>.</p>
971
- * <note>
975
+ * <note>
972
976
  * <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to
973
977
  * exported control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch
974
978
  * Pricing</a>.</p>
975
- * </note>
979
+ * </note>
976
980
  */
977
981
  logging?: Logging;
978
982
  /**
@@ -1103,12 +1107,12 @@ export interface Identity {
1103
1107
  */
1104
1108
  export interface KubernetesNetworkConfigResponse {
1105
1109
  /**
1106
- * <p>The CIDR block that Kubernetes pod and service IP addresses are assigned from.
1107
- * Kubernetes assigns addresses from an IPv4 CIDR block assigned to a subnet that the node
1108
- * is in. If you didn't specify a CIDR block when you created the cluster, then Kubernetes
1109
- * assigns addresses from either the 10.100.0.0/16 or 172.20.0.0/16 CIDR blocks. If this
1110
- * was specified, then it was specified when the cluster was created and it can't be
1111
- * changed.</p>
1110
+ * <p>The CIDR block that Kubernetes pod and service IP addresses are assigned from. Kubernetes
1111
+ * assigns addresses from an IPv4 CIDR block assigned to a subnet that the node is in. If
1112
+ * you didn't specify a CIDR block when you created the cluster, then Kubernetes assigns
1113
+ * addresses from either the <code>10.100.0.0/16</code> or <code>172.20.0.0/16</code> CIDR
1114
+ * blocks. If this was specified, then it was specified when the cluster was created and it
1115
+ * can't be changed.</p>
1112
1116
  */
1113
1117
  serviceIpv4Cidr?: string;
1114
1118
  /**
@@ -1531,13 +1535,13 @@ export declare enum CapacityTypes {
1531
1535
  * <code>CreateLaunchTemplate</code>
1532
1536
  * </a> in the Amazon EC2 API
1533
1537
  * Reference. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1534
- * <p>You must specify either the launch template ID or the launch template name in the
1538
+ * <p>You must specify either the launch template ID or the launch template name in the
1535
1539
  * request, but not both.</p>
1536
1540
  */
1537
1541
  export interface LaunchTemplateSpecification {
1538
1542
  /**
1539
1543
  * <p>The name of the launch template.</p>
1540
- * <p>You must specify either the launch template name or the launch template ID in the
1544
+ * <p>You must specify either the launch template name or the launch template ID in the
1541
1545
  * request, but not both.</p>
1542
1546
  */
1543
1547
  name?: string;
@@ -1548,7 +1552,7 @@ export interface LaunchTemplateSpecification {
1548
1552
  version?: string;
1549
1553
  /**
1550
1554
  * <p>The ID of the launch template.</p>
1551
- * <p>You must specify either the launch template ID or the launch template name in the
1555
+ * <p>You must specify either the launch template ID or the launch template name in the
1552
1556
  * request, but not both.</p>
1553
1557
  */
1554
1558
  id?: string;
@@ -1559,16 +1563,19 @@ export interface LaunchTemplateSpecification {
1559
1563
  */
1560
1564
  export interface RemoteAccessConfig {
1561
1565
  /**
1562
- * <p>The Amazon EC2 SSH key name that provides access for SSH communication with the
1563
- * nodes in the managed node group. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html">Amazon EC2 key pairs and Linux instances</a> in the <i>Amazon Elastic Compute Cloud User Guide for Linux Instances</i>.</p>
1566
+ * <p>The Amazon EC2 SSH key name that provides access for SSH communication with
1567
+ * the nodes in the managed node group. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html">Amazon EC2 key pairs and Linux instances</a> in the <i>Amazon Elastic Compute Cloud User Guide for Linux Instances</i>. For
1568
+ * Windows, an Amazon EC2 SSH key is used to obtain the RDP password. For more
1569
+ * information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-key-pairs.html">Amazon EC2 key pairs and Windows instances</a> in
1570
+ * the <i>Amazon Elastic Compute Cloud User Guide for Windows Instances</i>.</p>
1564
1571
  */
1565
1572
  ec2SshKey?: string;
1566
1573
  /**
1567
- * <p>The security group ids that are allowed SSH access (port 22) to the nodes. If you specify
1568
- * an Amazon EC2 SSH key but do not specify a source security group when you create
1569
- * a managed node group, then port 22 on the nodes is opened to the internet (0.0.0.0/0).
1570
- * For more information, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html">Security Groups for Your VPC</a> in the
1571
- * <i>Amazon Virtual Private Cloud User Guide</i>.</p>
1574
+ * <p>The security group IDs that are allowed SSH access (port 22) to the nodes. For
1575
+ * Windows, the port is 3389. If you specify an Amazon EC2 SSH key but don't
1576
+ * specify a source security group when you create a managed node group, then the port on
1577
+ * the nodes is opened to the internet (<code>0.0.0.0/0</code>). For more information, see
1578
+ * <a href="https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html">Security Groups for Your VPC</a> in the <i>Amazon Virtual Private Cloud User Guide</i>.</p>
1572
1579
  */
1573
1580
  sourceSecurityGroups?: string[];
1574
1581
  }
@@ -1590,19 +1597,19 @@ export interface NodegroupScalingConfig {
1590
1597
  maxSize?: number;
1591
1598
  /**
1592
1599
  * <p>The current number of nodes that the managed node group should maintain.</p>
1593
- * <important>
1600
+ * <important>
1594
1601
  * <p>If you use Cluster Autoscaler, you shouldn't change the desiredSize value
1595
1602
  * directly, as this can cause the Cluster Autoscaler to suddenly scale up or scale
1596
1603
  * down.</p>
1597
- * </important>
1598
- * <p>Whenever this parameter changes, the number of worker nodes in the node group is
1604
+ * </important>
1605
+ * <p>Whenever this parameter changes, the number of worker nodes in the node group is
1599
1606
  * updated to the specified size. If this parameter is given a value that is smaller than
1600
1607
  * the current number of running worker nodes, the necessary number of worker nodes are
1601
1608
  * terminated to match the given value.
1602
1609
  *
1603
1610
  * When using CloudFormation, no action occurs if you remove this parameter from your CFN
1604
1611
  * template.</p>
1605
- * <p>This parameter can be different from minSize in some cases, such as when starting with
1612
+ * <p>This parameter can be different from minSize in some cases, such as when starting with
1606
1613
  * extra hosts for testing. This parameter can also be different when you want to start
1607
1614
  * with an estimated number of needed hosts, but let Cluster Autoscaler reduce the number
1608
1615
  * if there are too many. When Cluster Autoscaler is used, the desiredSize parameter is
@@ -1667,8 +1674,9 @@ export interface CreateNodegroupRequest {
1667
1674
  scalingConfig?: NodegroupScalingConfig;
1668
1675
  /**
1669
1676
  * <p>The root device disk size (in GiB) for your node group instances. The default disk
1670
- * size is 20 GiB. If you specify <code>launchTemplate</code>, then don't specify <code>diskSize</code>,
1671
- * or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1677
+ * size is 20 GiB for Linux and Bottlerocket. The default disk size is 50 GiB for Windows.
1678
+ * If you specify <code>launchTemplate</code>, then don't specify <code>diskSize</code>, or the node group
1679
+ * deployment will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1672
1680
  */
1673
1681
  diskSize?: number;
1674
1682
  /**
@@ -1680,11 +1688,11 @@ export interface CreateNodegroupRequest {
1680
1688
  */
1681
1689
  subnets: string[] | undefined;
1682
1690
  /**
1683
- * <p>Specify the instance types for a node group. If you specify a GPU instance type, be
1684
- * sure to specify <code>AL2_x86_64_GPU</code> with the <code>amiType</code> parameter. If
1685
- * you specify <code>launchTemplate</code>, then you can specify zero or one instance type
1686
- * in your launch template <i>or</i> you can specify 0-20 instance types for
1687
- * <code>instanceTypes</code>. If however, you specify an instance type in your launch
1691
+ * <p>Specify the instance types for a node group. If you specify a GPU instance type, make
1692
+ * sure to also specify an applicable GPU AMI type with the <code>amiType</code> parameter.
1693
+ * If you specify <code>launchTemplate</code>, then you can specify zero or one instance
1694
+ * type in your launch template <i>or</i> you can specify 0-20 instance types
1695
+ * for <code>instanceTypes</code>. If however, you specify an instance type in your launch
1688
1696
  * template <i>and</i> specify any <code>instanceTypes</code>, the node group
1689
1697
  * deployment will fail. If you don't specify an instance type in a launch template or for
1690
1698
  * <code>instanceTypes</code>, then <code>t3.medium</code> is used, by default. If you
@@ -1694,19 +1702,20 @@ export interface CreateNodegroupRequest {
1694
1702
  */
1695
1703
  instanceTypes?: string[];
1696
1704
  /**
1697
- * <p>The AMI type for your node group. GPU instance types should use the
1698
- * <code>AL2_x86_64_GPU</code> AMI type. Non-GPU instances should use the
1699
- * <code>AL2_x86_64</code> AMI type. Arm instances should use the
1700
- * <code>AL2_ARM_64</code> AMI type. All types use the Amazon EKS optimized
1701
- * Amazon Linux 2 AMI. If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI,
1705
+ * <p>The AMI type for your node group. If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI,
1702
1706
  * then don't specify <code>amiType</code>, or the node group deployment
1703
- * will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1707
+ * will fail. If your launch template uses a Windows custom AMI, then add
1708
+ * <code>eks:kube-proxy-windows</code> to your Windows nodes <code>rolearn</code> in
1709
+ * the <code>aws-auth</code>
1710
+ * <code>ConfigMap</code>. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1704
1711
  */
1705
1712
  amiType?: AMITypes | string;
1706
1713
  /**
1707
- * <p>The remote access (SSH) configuration to use with your node group. If you specify <code>launchTemplate</code>,
1708
- * then don't specify <code>remoteAccess</code>, or the node group deployment
1709
- * will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1714
+ * <p>The remote access configuration to use with your node group.
1715
+ * For Linux, the protocol is SSH. For Windows, the protocol is RDP.
1716
+ * If you specify <code>launchTemplate</code>, then don't specify
1717
+ * <code>remoteAccess</code>, or the node group deployment will fail.
1718
+ * For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1710
1719
  */
1711
1720
  remoteAccess?: RemoteAccessConfig;
1712
1721
  /**
@@ -1771,10 +1780,13 @@ export interface CreateNodegroupRequest {
1771
1780
  version?: string;
1772
1781
  /**
1773
1782
  * <p>The AMI version of the Amazon EKS optimized AMI to use with your node group.
1774
- * By default, the latest available AMI version for the node group's current Kubernetes
1775
- * version is used. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux 2 AMI versions</a> in the <i>Amazon EKS User Guide</i>.
1776
- * If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify <code>releaseVersion</code>,
1777
- * or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1783
+ * By default, the latest available AMI version for the node group's current Kubernetes version
1784
+ * is used. For information about Linux versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux AMI versions</a> in the <i>Amazon EKS User Guide</i>. Amazon EKS managed node groups support the November 2022 and later releases of the
1785
+ * Windows AMIs. For information about Windows versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-versions-windows.html">Amazon EKS optimized Windows AMI versions</a> in the
1786
+ * <i>Amazon EKS User Guide</i>.</p>
1787
+ * <p>If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify
1788
+ * <code>releaseVersion</code>, or the node group deployment will fail.
1789
+ * For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
1778
1790
  */
1779
1791
  releaseVersion?: string;
1780
1792
  }
@@ -1805,58 +1817,58 @@ export declare enum NodegroupIssueCode {
1805
1817
  export interface Issue {
1806
1818
  /**
1807
1819
  * <p>A brief description of the error.</p>
1808
- * <ul>
1820
+ * <ul>
1809
1821
  * <li>
1810
- * <p>
1822
+ * <p>
1811
1823
  * <b>AccessDenied</b>: Amazon EKS or one or
1812
1824
  * more of your managed nodes is failing to authenticate or authorize with your
1813
1825
  * Kubernetes cluster API server.</p>
1814
1826
  * </li>
1815
1827
  * <li>
1816
- * <p>
1828
+ * <p>
1817
1829
  * <b>AsgInstanceLaunchFailures</b>: Your Auto Scaling group is experiencing failures while attempting to launch
1818
1830
  * instances.</p>
1819
1831
  * </li>
1820
1832
  * <li>
1821
- * <p>
1833
+ * <p>
1822
1834
  * <b>AutoScalingGroupNotFound</b>: We couldn't find
1823
1835
  * the Auto Scaling group associated with the managed node group. You may be
1824
1836
  * able to recreate an Auto Scaling group with the same settings to
1825
1837
  * recover.</p>
1826
1838
  * </li>
1827
1839
  * <li>
1828
- * <p>
1840
+ * <p>
1829
1841
  * <b>ClusterUnreachable</b>: Amazon EKS or one
1830
1842
  * or more of your managed nodes is unable to to communicate with your Kubernetes
1831
1843
  * cluster API server. This can happen if there are network disruptions or if API
1832
1844
  * servers are timing out processing requests. </p>
1833
1845
  * </li>
1834
1846
  * <li>
1835
- * <p>
1847
+ * <p>
1836
1848
  * <b>Ec2LaunchTemplateNotFound</b>: We couldn't find
1837
1849
  * the Amazon EC2 launch template for your managed node group. You may be
1838
1850
  * able to recreate a launch template with the same settings to recover.</p>
1839
1851
  * </li>
1840
1852
  * <li>
1841
- * <p>
1853
+ * <p>
1842
1854
  * <b>Ec2LaunchTemplateVersionMismatch</b>: The Amazon EC2 launch template version for your managed node group does not
1843
1855
  * match the version that Amazon EKS created. You may be able to revert to
1844
1856
  * the version that Amazon EKS created to recover.</p>
1845
1857
  * </li>
1846
1858
  * <li>
1847
- * <p>
1859
+ * <p>
1848
1860
  * <b>Ec2SecurityGroupDeletionFailure</b>: We could not
1849
1861
  * delete the remote access security group for your managed node group. Remove any
1850
1862
  * dependencies from the security group.</p>
1851
1863
  * </li>
1852
1864
  * <li>
1853
- * <p>
1865
+ * <p>
1854
1866
  * <b>Ec2SecurityGroupNotFound</b>: We couldn't find
1855
1867
  * the cluster security group for the cluster. You must recreate your
1856
1868
  * cluster.</p>
1857
1869
  * </li>
1858
1870
  * <li>
1859
- * <p>
1871
+ * <p>
1860
1872
  * <b>Ec2SubnetInvalidConfiguration</b>: One or more
1861
1873
  * Amazon EC2 subnets specified for a node group do not automatically
1862
1874
  * assign public IP addresses to instances launched into it. If you want your
@@ -1867,36 +1879,36 @@ export interface Issue {
1867
1879
  * <i>Amazon VPC User Guide</i>.</p>
1868
1880
  * </li>
1869
1881
  * <li>
1870
- * <p>
1882
+ * <p>
1871
1883
  * <b>IamInstanceProfileNotFound</b>: We couldn't find
1872
1884
  * the IAM instance profile for your managed node group. You may be
1873
1885
  * able to recreate an instance profile with the same settings to recover.</p>
1874
1886
  * </li>
1875
1887
  * <li>
1876
- * <p>
1888
+ * <p>
1877
1889
  * <b>IamNodeRoleNotFound</b>: We couldn't find the
1878
1890
  * IAM role for your managed node group. You may be able to
1879
1891
  * recreate an IAM role with the same settings to recover.</p>
1880
1892
  * </li>
1881
1893
  * <li>
1882
- * <p>
1894
+ * <p>
1883
1895
  * <b>InstanceLimitExceeded</b>: Your Amazon Web Services account is unable to launch any more instances of the specified instance
1884
1896
  * type. You may be able to request an Amazon EC2 instance limit increase
1885
1897
  * to recover.</p>
1886
1898
  * </li>
1887
1899
  * <li>
1888
- * <p>
1900
+ * <p>
1889
1901
  * <b>InsufficientFreeAddresses</b>: One or more of the
1890
1902
  * subnets associated with your managed node group does not have enough available
1891
1903
  * IP addresses for new nodes.</p>
1892
1904
  * </li>
1893
1905
  * <li>
1894
- * <p>
1906
+ * <p>
1895
1907
  * <b>InternalFailure</b>: These errors are usually
1896
1908
  * caused by an Amazon EKS server-side issue.</p>
1897
1909
  * </li>
1898
1910
  * <li>
1899
- * <p>
1911
+ * <p>
1900
1912
  * <b>NodeCreationFailure</b>: Your launched instances
1901
1913
  * are unable to register with your Amazon EKS cluster. Common causes of
1902
1914
  * this failure are insufficient <a href="https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html">node IAM
@@ -2030,10 +2042,10 @@ export interface Nodegroup {
2030
2042
  nodeRole?: string;
2031
2043
  /**
2032
2044
  * <p>The Kubernetes labels applied to the nodes in the node group.</p>
2033
- * <note>
2045
+ * <note>
2034
2046
  * <p>Only labels that are applied with the Amazon EKS API are shown here. There
2035
2047
  * may be other Kubernetes labels applied to the nodes in this group.</p>
2036
- * </note>
2048
+ * </note>
2037
2049
  */
2038
2050
  labels?: Record<string, string>;
2039
2051
  /**
@@ -2184,9 +2196,9 @@ export interface DescribeAddonResponse {
2184
2196
  }
2185
2197
  export interface DescribeAddonConfigurationRequest {
2186
2198
  /**
2187
- * <p>The name of the add-on. The name must match one of the names returned by <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonVersions.html">
2199
+ * <p>The name of the add-on. The name must match one of the names that <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonVersions.html">
2188
2200
  * <code>DescribeAddonVersions</code>
2189
- * </a>.</p>
2201
+ * </a> returns.</p>
2190
2202
  */
2191
2203
  addonName: string | undefined;
2192
2204
  /**
@@ -2208,7 +2220,8 @@ export interface DescribeAddonConfigurationResponse {
2208
2220
  */
2209
2221
  addonVersion?: string;
2210
2222
  /**
2211
- * <p>A JSON schema used to validate provided configuration values when creating or updating an addon.</p>
2223
+ * <p>A JSON schema that's used to validate the configuration values that you provide when
2224
+ * an addon is created or updated.</p>
2212
2225
  */
2213
2226
  configurationSchema?: string;
2214
2227
  }
@@ -2226,10 +2239,10 @@ export interface DescribeAddonVersionsRequest {
2226
2239
  * <code>DescribeAddonVersionsRequest</code> where <code>maxResults</code> was used and
2227
2240
  * the results exceeded the value of that parameter. Pagination continues from the end of
2228
2241
  * the previous results that returned the <code>nextToken</code> value.</p>
2229
- * <note>
2242
+ * <note>
2230
2243
  * <p>This token should be treated as an opaque identifier that is used only to
2231
2244
  * retrieve the next items in a list and not for other programmatic purposes.</p>
2232
- * </note>
2245
+ * </note>
2233
2246
  */
2234
2247
  nextToken?: string;
2235
2248
  /**
@@ -2265,10 +2278,10 @@ export interface DescribeAddonVersionsResponse {
2265
2278
  * <code>DescribeAddonVersionsResponse</code> where <code>maxResults</code> was used
2266
2279
  * and the results exceeded the value of that parameter. Pagination continues from the end
2267
2280
  * of the previous results that returned the <code>nextToken</code> value.</p>
2268
- * <note>
2281
+ * <note>
2269
2282
  * <p>This token should be treated as an opaque identifier that is used only to
2270
2283
  * retrieve the next items in a list and not for other programmatic purposes.</p>
2271
- * </note>
2284
+ * </note>
2272
2285
  */
2273
2286
  nextToken?: string;
2274
2287
  }
@@ -2497,10 +2510,10 @@ export interface ListAddonsRequest {
2497
2510
  * <code>ListAddonsRequest</code> where <code>maxResults</code> was used and the
2498
2511
  * results exceeded the value of that parameter. Pagination continues from the end of the
2499
2512
  * previous results that returned the <code>nextToken</code> value.</p>
2500
- * <note>
2513
+ * <note>
2501
2514
  * <p>This token should be treated as an opaque identifier that is used only to
2502
2515
  * retrieve the next items in a list and not for other programmatic purposes.</p>
2503
- * </note>
2516
+ * </note>
2504
2517
  */
2505
2518
  nextToken?: string;
2506
2519
  }
@@ -2514,10 +2527,10 @@ export interface ListAddonsResponse {
2514
2527
  * <code>ListAddonsResponse</code> where <code>maxResults</code> was used and the
2515
2528
  * results exceeded the value of that parameter. Pagination continues from the end of the
2516
2529
  * previous results that returned the <code>nextToken</code> value.</p>
2517
- * <note>
2530
+ * <note>
2518
2531
  * <p>This token should be treated as an opaque identifier that is used only to
2519
2532
  * retrieve the next items in a list and not for other programmatic purposes.</p>
2520
- * </note>
2533
+ * </note>
2521
2534
  */
2522
2535
  nextToken?: string;
2523
2536
  }
@@ -2538,10 +2551,10 @@ export interface ListClustersRequest {
2538
2551
  * <code>ListClusters</code> request where <code>maxResults</code> was used and the
2539
2552
  * results exceeded the value of that parameter. Pagination continues from the end of the
2540
2553
  * previous results that returned the <code>nextToken</code> value.</p>
2541
- * <note>
2554
+ * <note>
2542
2555
  * <p>This token should be treated as an opaque identifier that is used only to
2543
2556
  * retrieve the next items in a list and not for other programmatic purposes.</p>
2544
- * </note>
2557
+ * </note>
2545
2558
  */
2546
2559
  nextToken?: string;
2547
2560
  /**
@@ -2877,7 +2890,7 @@ export interface UpdateAddonRequest {
2877
2890
  /**
2878
2891
  * <p>The Amazon Resource Name (ARN) of an existing IAM role to bind to the add-on's service account. The role must be assigned the IAM permissions required by the add-on. If you don't specify an existing IAM role, then the add-on uses the
2879
2892
  * permissions assigned to the node IAM role. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html">Amazon EKS node IAM role</a> in the <i>Amazon EKS User Guide</i>.</p>
2880
- * <note>
2893
+ * <note>
2881
2894
  * <p>To specify an existing IAM role, you must have an IAM OpenID Connect (OIDC) provider created for
2882
2895
  * your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html">Enabling
2883
2896
  * IAM roles for service accounts on your cluster</a> in the
@@ -2889,20 +2902,20 @@ export interface UpdateAddonRequest {
2889
2902
  * <p>How to resolve field value conflicts for an Amazon EKS add-on if you've
2890
2903
  * changed a value from the Amazon EKS default value. Conflicts are handled based
2891
2904
  * on the option you choose:</p>
2892
- * <ul>
2905
+ * <ul>
2893
2906
  * <li>
2894
- * <p>
2907
+ * <p>
2895
2908
  * <b>None</b> – Amazon EKS doesn't
2896
2909
  * change the value. The update might fail.</p>
2897
2910
  * </li>
2898
2911
  * <li>
2899
- * <p>
2912
+ * <p>
2900
2913
  * <b>Overwrite</b> – Amazon EKS
2901
2914
  * overwrites the changed value back to the Amazon EKS default
2902
2915
  * value.</p>
2903
2916
  * </li>
2904
2917
  * <li>
2905
- * <p>
2918
+ * <p>
2906
2919
  * <b>Preserve</b> – Amazon EKS
2907
2920
  * preserves the value. If you choose this option, we recommend that you test any
2908
2921
  * field and value changes on a non-production cluster before updating the add-on
@@ -2917,8 +2930,8 @@ export interface UpdateAddonRequest {
2917
2930
  */
2918
2931
  clientRequestToken?: string;
2919
2932
  /**
2920
- * <p>The set of configuration values for the add-on being created. Whatever values provided here are validated against the schema from <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonConfiguration.html">DescribeAddonConfiguration</a>
2921
- * </p>
2933
+ * <p>The set of configuration values for the add-on that's created. The values that you
2934
+ * provide are validated against the schema in <a href="https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeAddonConfiguration.html">DescribeAddonConfiguration</a>.</p>
2922
2935
  */
2923
2936
  configurationValues?: string;
2924
2937
  }
@@ -2945,11 +2958,11 @@ export interface UpdateClusterConfigRequest {
2945
2958
  * <i>
2946
2959
  * <i>Amazon EKS User Guide</i>
2947
2960
  * </i>.</p>
2948
- * <note>
2961
+ * <note>
2949
2962
  * <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to
2950
2963
  * exported control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch
2951
2964
  * Pricing</a>.</p>
2952
- * </note>
2965
+ * </note>
2953
2966
  */
2954
2967
  logging?: Logging;
2955
2968
  /**
@@ -3075,10 +3088,13 @@ export interface UpdateNodegroupVersionRequest {
3075
3088
  version?: string;
3076
3089
  /**
3077
3090
  * <p>The AMI version of the Amazon EKS optimized AMI to use for the update. By
3078
- * default, the latest available AMI version for the node group's Kubernetes version is
3079
- * used. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux 2 AMI versions </a> in the <i>Amazon EKS User Guide</i>.
3080
- * If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify <code>releaseVersion</code>,
3081
- * or the node group update will fail. For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
3091
+ * default, the latest available AMI version for the node group's Kubernetes version is used.
3092
+ * For information about Linux versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux AMI versions</a> in the <i>Amazon EKS User Guide</i>. Amazon EKS managed node groups support the November 2022 and later releases of the
3093
+ * Windows AMIs. For information about Windows versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-versions-windows.html">Amazon EKS optimized Windows AMI versions</a> in the
3094
+ * <i>Amazon EKS User Guide</i>.</p>
3095
+ * <p>If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify
3096
+ * <code>releaseVersion</code>, or the node group update will fail.
3097
+ * For more information about using launch templates with Amazon EKS, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch template support</a> in the <i>Amazon EKS User Guide</i>.</p>
3082
3098
  */
3083
3099
  releaseVersion?: string;
3084
3100
  /**