aws-sdk-eks 1.138.0 → 1.139.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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a839b4da440cd4aff716ff553d4dc8185ad4475ccc1d2c3bd15cb1f9d8203d3d
4
- data.tar.gz: b6ecfc2a337511c20c601da1066e1f4cf40d7c6b5770e452b5b9d0653dee3d62
3
+ metadata.gz: bfafb3c4a993afbab984bdb91bc15f1bcb95d2aa5c6014653fcdf609c9b29ece
4
+ data.tar.gz: 4079bd72a94979ca6da8299cb0f84ee50658ceeded917e1ebe29d5f943117102
5
5
  SHA512:
6
- metadata.gz: 1e5b1f7218ff939f712867e558028f5c0af3b9b5ae3159d9f496872e92e5b51583ee34ac8e9c20e9e8d0b8ccab5f66b4375df40d3a93b00bf8aef06af9428741
7
- data.tar.gz: 3b7ca320fe01ceccb78a530b9e1bc0dba074f0ab09b8bb0af42ac57a2826b0ba2d17a46e924b89c2ae6c7509ac2268e18cbbe1d797b9ec36f4467d0f6268d885
6
+ metadata.gz: 46bfcabcb9b0fb7087ac0b931ec1e5eeb22169a11bf3ba39ab4e4da8daf23b2339a895763149253b69cf7ab363257e38527cb3058822f64f631790d8ff0ec2b4
7
+ data.tar.gz: d8042d0978684917d8b55381d1f5c7da5f1ffd672ab35f4f5e6128c30669c3075b05dbeab8fa7938f038c804a6a403985d9d4e1da1b68ddcef01e03a31c4f2a7
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.139.0 (2025-06-11)
5
+ ------------------
6
+
7
+ * Feature - Release for EKS Pod Identity Cross Account feature and disableSessionTags flag.
8
+
4
9
  1.138.0 (2025-06-02)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.138.0
1
+ 1.139.0
@@ -927,11 +927,11 @@ module Aws::EKS
927
927
  # `DescribeAddonConfiguration`.
928
928
  #
929
929
  # @option params [Array<Types::AddonPodIdentityAssociations>] :pod_identity_associations
930
- # An array of Pod Identity Assocations to be created. Each EKS Pod
931
- # Identity association maps a Kubernetes service account to an IAM Role.
930
+ # An array of EKS Pod Identity associations to be created. Each
931
+ # association maps a Kubernetes service account to an IAM role.
932
932
  #
933
933
  # For more information, see [Attach an IAM Role to an Amazon EKS add-on
934
- # using Pod Identity][1] in the *Amazon EKS User Guide*.
934
+ # using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
935
935
  #
936
936
  #
937
937
  #
@@ -1019,9 +1019,10 @@ module Aws::EKS
1019
1019
  # You can use the `endpointPublicAccess` and `endpointPrivateAccess`
1020
1020
  # parameters to enable or disable public and private access to your
1021
1021
  # cluster's Kubernetes API server endpoint. By default, public access
1022
- # is enabled, and private access is disabled. For more information, see
1023
- # [Amazon EKS Cluster Endpoint Access Control][1] in the <i> <i>Amazon
1024
- # EKS User Guide</i> </i>.
1022
+ # is enabled, and private access is disabled. The endpoint domain name
1023
+ # and IP address family depends on the value of the `ipFamily` for the
1024
+ # cluster. For more information, see [Amazon EKS Cluster Endpoint Access
1025
+ # Control][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
1025
1026
  #
1026
1027
  # You can use the `logging` parameter to enable or disable exporting the
1027
1028
  # Kubernetes control plane logs for your cluster to CloudWatch Logs. By
@@ -1146,8 +1147,8 @@ module Aws::EKS
1146
1147
  # If you set this value to `False` when creating a cluster, the default
1147
1148
  # networking add-ons will not be installed.
1148
1149
  #
1149
- # The default networking addons include vpc-cni, coredns, and
1150
- # kube-proxy.
1150
+ # The default networking add-ons include `vpc-cni`, `coredns`, and
1151
+ # `kube-proxy`.
1151
1152
  #
1152
1153
  # Use this option when you plan to install third-party alternative
1153
1154
  # add-ons or self-manage the default networking add-ons.
@@ -1951,31 +1952,49 @@ module Aws::EKS
1951
1952
 
1952
1953
  # Creates an EKS Pod Identity association between a service account in
1953
1954
  # an Amazon EKS cluster and an IAM role with *EKS Pod Identity*. Use EKS
1954
- # Pod Identity to give temporary IAM credentials to pods and the
1955
+ # Pod Identity to give temporary IAM credentials to Pods and the
1955
1956
  # credentials are rotated automatically.
1956
1957
  #
1957
1958
  # Amazon EKS Pod Identity associations provide the ability to manage
1958
1959
  # credentials for your applications, similar to the way that Amazon EC2
1959
1960
  # instance profiles provide credentials to Amazon EC2 instances.
1960
1961
  #
1961
- # If a pod uses a service account that has an association, Amazon EKS
1962
- # sets environment variables in the containers of the pod. The
1962
+ # If a Pod uses a service account that has an association, Amazon EKS
1963
+ # sets environment variables in the containers of the Pod. The
1963
1964
  # environment variables configure the Amazon Web Services SDKs,
1964
1965
  # including the Command Line Interface, to use the EKS Pod Identity
1965
1966
  # credentials.
1966
1967
  #
1967
- # Pod Identity is a simpler method than *IAM roles for service
1968
+ # EKS Pod Identity is a simpler method than *IAM roles for service
1968
1969
  # accounts*, as this method doesn't use OIDC identity providers.
1969
- # Additionally, you can configure a role for Pod Identity once, and
1970
+ # Additionally, you can configure a role for EKS Pod Identity once, and
1970
1971
  # reuse it across clusters.
1971
1972
  #
1973
+ # Similar to Amazon Web Services IAM behavior, EKS Pod Identity
1974
+ # associations are eventually consistent, and may take several seconds
1975
+ # to be effective after the initial API call returns successfully. You
1976
+ # must design your applications to account for these potential delays.
1977
+ # We recommend that you don’t include association create/updates in the
1978
+ # critical, high-availability code paths of your application. Instead,
1979
+ # make changes in a separate initialization or setup routine that you
1980
+ # run less frequently.
1981
+ #
1982
+ # You can set a *target IAM role* in the same or a different account for
1983
+ # advanced scenarios. With a target role, EKS Pod Identity automatically
1984
+ # performs two role assumptions in sequence: first assuming the role in
1985
+ # the association that is in this account, then using those credentials
1986
+ # to assume the target IAM role. This process provides your Pod with
1987
+ # temporary credentials that have the permissions defined in the target
1988
+ # role, allowing secure access to resources in another Amazon Web
1989
+ # Services account.
1990
+ #
1972
1991
  # @option params [required, String] :cluster_name
1973
- # The name of the cluster to create the association in.
1992
+ # The name of the cluster to create the EKS Pod Identity association in.
1974
1993
  #
1975
1994
  # @option params [required, String] :namespace
1976
1995
  # The name of the Kubernetes namespace inside the cluster to create the
1977
- # association in. The service account and the pods that use the service
1978
- # account must be in this namespace.
1996
+ # EKS Pod Identity association in. The service account and the Pods that
1997
+ # use the service account must be in this namespace.
1979
1998
  #
1980
1999
  # @option params [required, String] :service_account
1981
2000
  # The name of the Kubernetes service account inside the cluster to
@@ -1984,7 +2003,7 @@ module Aws::EKS
1984
2003
  # @option params [required, String] :role_arn
1985
2004
  # The Amazon Resource Name (ARN) of the IAM role to associate with the
1986
2005
  # service account. The EKS Pod Identity agent manages credentials to
1987
- # assume this role for applications in the containers in the pods that
2006
+ # assume this role for applications in the containers in the Pods that
1988
2007
  # use this service account.
1989
2008
  #
1990
2009
  # @option params [String] :client_request_token
@@ -2024,6 +2043,51 @@ module Aws::EKS
2024
2043
  # values with this prefix. Tags with this prefix do not count against
2025
2044
  # your tags per resource limit.
2026
2045
  #
2046
+ # @option params [Boolean] :disable_session_tags
2047
+ # Disable the automatic sessions tags that are appended by EKS Pod
2048
+ # Identity.
2049
+ #
2050
+ # EKS Pod Identity adds a pre-defined set of session tags when it
2051
+ # assumes the role. You can use these tags to author a single role that
2052
+ # can work across resources by allowing access to Amazon Web Services
2053
+ # resources based on matching tags. By default, EKS Pod Identity
2054
+ # attaches six tags, including tags for cluster name, namespace, and
2055
+ # service account name. For the list of tags added by EKS Pod Identity,
2056
+ # see [List of session tags added by EKS Pod Identity][1] in the *Amazon
2057
+ # EKS User Guide*.
2058
+ #
2059
+ # Amazon Web Services compresses inline session policies, managed policy
2060
+ # ARNs, and session tags into a packed binary format that has a separate
2061
+ # limit. If you receive a `PackedPolicyTooLarge` error indicating the
2062
+ # packed binary format has exceeded the size limit, you can attempt to
2063
+ # reduce the size by disabling the session tags added by EKS Pod
2064
+ # Identity.
2065
+ #
2066
+ #
2067
+ #
2068
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-abac.html#pod-id-abac-tags
2069
+ #
2070
+ # @option params [String] :target_role_arn
2071
+ # The Amazon Resource Name (ARN) of the target IAM role to associate
2072
+ # with the service account. This role is assumed by using the EKS Pod
2073
+ # Identity association role, then the credentials for this role are
2074
+ # injected into the Pod.
2075
+ #
2076
+ # When you run applications on Amazon EKS, your application might need
2077
+ # to access Amazon Web Services resources from a different role that
2078
+ # exists in the same or different Amazon Web Services account. For
2079
+ # example, your application running in “Account A” might need to access
2080
+ # resources, such as Amazon S3 buckets in “Account B” or within “Account
2081
+ # A” itself. You can create a association to access Amazon Web Services
2082
+ # resources in “Account B” by creating two IAM roles: a role in “Account
2083
+ # A” and a role in “Account B” (which can be the same or different
2084
+ # account), each with the necessary trust and permission policies. After
2085
+ # you provide these roles in the *IAM role* and *Target IAM role*
2086
+ # fields, EKS will perform role chaining to ensure your application gets
2087
+ # the required permissions. This means Role A will assume Role B,
2088
+ # allowing your Pods to securely access resources like S3 buckets in the
2089
+ # target account.
2090
+ #
2027
2091
  # @return [Types::CreatePodIdentityAssociationResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
2028
2092
  #
2029
2093
  # * {Types::CreatePodIdentityAssociationResponse#association #association} => Types::PodIdentityAssociation
@@ -2039,6 +2103,8 @@ module Aws::EKS
2039
2103
  # tags: {
2040
2104
  # "TagKey" => "TagValue",
2041
2105
  # },
2106
+ # disable_session_tags: false,
2107
+ # target_role_arn: "String",
2042
2108
  # })
2043
2109
  #
2044
2110
  # @example Response structure
@@ -2054,6 +2120,9 @@ module Aws::EKS
2054
2120
  # resp.association.created_at #=> Time
2055
2121
  # resp.association.modified_at #=> Time
2056
2122
  # resp.association.owner_arn #=> String
2123
+ # resp.association.disable_session_tags #=> Boolean
2124
+ # resp.association.target_role_arn #=> String
2125
+ # resp.association.external_id #=> String
2057
2126
  #
2058
2127
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/CreatePodIdentityAssociation AWS API Documentation
2059
2128
  #
@@ -2504,6 +2573,9 @@ module Aws::EKS
2504
2573
  # resp.association.created_at #=> Time
2505
2574
  # resp.association.modified_at #=> Time
2506
2575
  # resp.association.owner_arn #=> String
2576
+ # resp.association.disable_session_tags #=> Boolean
2577
+ # resp.association.target_role_arn #=> String
2578
+ # resp.association.external_id #=> String
2507
2579
  #
2508
2580
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/DeletePodIdentityAssociation AWS API Documentation
2509
2581
  #
@@ -3420,6 +3492,9 @@ module Aws::EKS
3420
3492
  # resp.association.created_at #=> Time
3421
3493
  # resp.association.modified_at #=> Time
3422
3494
  # resp.association.owner_arn #=> String
3495
+ # resp.association.disable_session_tags #=> Boolean
3496
+ # resp.association.target_role_arn #=> String
3497
+ # resp.association.external_id #=> String
3423
3498
  #
3424
3499
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/DescribePodIdentityAssociation AWS API Documentation
3425
3500
  #
@@ -4782,13 +4857,13 @@ module Aws::EKS
4782
4857
  # `DescribeAddonConfiguration`.
4783
4858
  #
4784
4859
  # @option params [Array<Types::AddonPodIdentityAssociations>] :pod_identity_associations
4785
- # An array of Pod Identity Assocations to be updated. Each EKS Pod
4786
- # Identity association maps a Kubernetes service account to an IAM Role.
4787
- # If this value is left blank, no change. If an empty array is provided,
4788
- # existing Pod Identity Assocations owned by the Addon are deleted.
4860
+ # An array of EKS Pod Identity associations to be updated. Each
4861
+ # association maps a Kubernetes service account to an IAM role. If this
4862
+ # value is left blank, no change. If an empty array is provided,
4863
+ # existing associations owned by the add-on are deleted.
4789
4864
  #
4790
4865
  # For more information, see [Attach an IAM Role to an Amazon EKS add-on
4791
- # using Pod Identity][1] in the *Amazon EKS User Guide*.
4866
+ # using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
4792
4867
  #
4793
4868
  #
4794
4869
  #
@@ -4862,8 +4937,8 @@ module Aws::EKS
4862
4937
  # * You can also use this API operation to enable or disable public and
4863
4938
  # private access to your cluster's Kubernetes API server endpoint. By
4864
4939
  # default, public access is enabled, and private access is disabled.
4865
- # For more information, see [Amazon EKS cluster endpoint access
4866
- # control][3] in the <i> <i>Amazon EKS User Guide</i> </i>.
4940
+ # For more information, see [ Cluster API server endpoint][3] in the
4941
+ # <i> <i>Amazon EKS User Guide</i> </i>.
4867
4942
  #
4868
4943
  # * You can also use this API operation to choose different subnets and
4869
4944
  # security groups for the cluster. You must specify at least two
@@ -5464,11 +5539,31 @@ module Aws::EKS
5464
5539
  req.send_request(options)
5465
5540
  end
5466
5541
 
5467
- # Updates a EKS Pod Identity association. Only the IAM role can be
5468
- # changed; an association can't be moved between clusters, namespaces,
5469
- # or service accounts. If you need to edit the namespace or service
5470
- # account, you need to delete the association and then create a new
5471
- # association with your desired settings.
5542
+ # Updates a EKS Pod Identity association. In an update, you can change
5543
+ # the IAM role, the target IAM role, or `disableSessionTags`. You must
5544
+ # change at least one of these in an update. An association can't be
5545
+ # moved between clusters, namespaces, or service accounts. If you need
5546
+ # to edit the namespace or service account, you need to delete the
5547
+ # association and then create a new association with your desired
5548
+ # settings.
5549
+ #
5550
+ # Similar to Amazon Web Services IAM behavior, EKS Pod Identity
5551
+ # associations are eventually consistent, and may take several seconds
5552
+ # to be effective after the initial API call returns successfully. You
5553
+ # must design your applications to account for these potential delays.
5554
+ # We recommend that you don’t include association create/updates in the
5555
+ # critical, high-availability code paths of your application. Instead,
5556
+ # make changes in a separate initialization or setup routine that you
5557
+ # run less frequently.
5558
+ #
5559
+ # You can set a *target IAM role* in the same or a different account for
5560
+ # advanced scenarios. With a target role, EKS Pod Identity automatically
5561
+ # performs two role assumptions in sequence: first assuming the role in
5562
+ # the association that is in this account, then using those credentials
5563
+ # to assume the target IAM role. This process provides your Pod with
5564
+ # temporary credentials that have the permissions defined in the target
5565
+ # role, allowing secure access to resources in another Amazon Web
5566
+ # Services account.
5472
5567
  #
5473
5568
  # @option params [required, String] :cluster_name
5474
5569
  # The name of the cluster that you want to update the association in.
@@ -5477,7 +5572,7 @@ module Aws::EKS
5477
5572
  # The ID of the association to be updated.
5478
5573
  #
5479
5574
  # @option params [String] :role_arn
5480
- # The new IAM role to change the
5575
+ # The new IAM role to change in the association.
5481
5576
  #
5482
5577
  # @option params [String] :client_request_token
5483
5578
  # A unique, case-sensitive identifier that you provide to ensure the
@@ -5486,6 +5581,51 @@ module Aws::EKS
5486
5581
  # **A suitable default value is auto-generated.** You should normally
5487
5582
  # not need to pass this option.**
5488
5583
  #
5584
+ # @option params [Boolean] :disable_session_tags
5585
+ # Disable the automatic sessions tags that are appended by EKS Pod
5586
+ # Identity.
5587
+ #
5588
+ # EKS Pod Identity adds a pre-defined set of session tags when it
5589
+ # assumes the role. You can use these tags to author a single role that
5590
+ # can work across resources by allowing access to Amazon Web Services
5591
+ # resources based on matching tags. By default, EKS Pod Identity
5592
+ # attaches six tags, including tags for cluster name, namespace, and
5593
+ # service account name. For the list of tags added by EKS Pod Identity,
5594
+ # see [List of session tags added by EKS Pod Identity][1] in the *Amazon
5595
+ # EKS User Guide*.
5596
+ #
5597
+ # Amazon Web Services compresses inline session policies, managed policy
5598
+ # ARNs, and session tags into a packed binary format that has a separate
5599
+ # limit. If you receive a `PackedPolicyTooLarge` error indicating the
5600
+ # packed binary format has exceeded the size limit, you can attempt to
5601
+ # reduce the size by disabling the session tags added by EKS Pod
5602
+ # Identity.
5603
+ #
5604
+ #
5605
+ #
5606
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-abac.html#pod-id-abac-tags
5607
+ #
5608
+ # @option params [String] :target_role_arn
5609
+ # The Amazon Resource Name (ARN) of the target IAM role to associate
5610
+ # with the service account. This role is assumed by using the EKS Pod
5611
+ # Identity association role, then the credentials for this role are
5612
+ # injected into the Pod.
5613
+ #
5614
+ # When you run applications on Amazon EKS, your application might need
5615
+ # to access Amazon Web Services resources from a different role that
5616
+ # exists in the same or different Amazon Web Services account. For
5617
+ # example, your application running in “Account A” might need to access
5618
+ # resources, such as buckets in “Account B” or within “Account A”
5619
+ # itself. You can create a association to access Amazon Web Services
5620
+ # resources in “Account B” by creating two IAM roles: a role in “Account
5621
+ # A” and a role in “Account B” (which can be the same or different
5622
+ # account), each with the necessary trust and permission policies. After
5623
+ # you provide these roles in the *IAM role* and *Target IAM role*
5624
+ # fields, EKS will perform role chaining to ensure your application gets
5625
+ # the required permissions. This means Role A will assume Role B,
5626
+ # allowing your Pods to securely access resources like S3 buckets in the
5627
+ # target account.
5628
+ #
5489
5629
  # @return [Types::UpdatePodIdentityAssociationResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
5490
5630
  #
5491
5631
  # * {Types::UpdatePodIdentityAssociationResponse#association #association} => Types::PodIdentityAssociation
@@ -5497,6 +5637,8 @@ module Aws::EKS
5497
5637
  # association_id: "String", # required
5498
5638
  # role_arn: "String",
5499
5639
  # client_request_token: "String",
5640
+ # disable_session_tags: false,
5641
+ # target_role_arn: "String",
5500
5642
  # })
5501
5643
  #
5502
5644
  # @example Response structure
@@ -5512,6 +5654,9 @@ module Aws::EKS
5512
5654
  # resp.association.created_at #=> Time
5513
5655
  # resp.association.modified_at #=> Time
5514
5656
  # resp.association.owner_arn #=> String
5657
+ # resp.association.disable_session_tags #=> Boolean
5658
+ # resp.association.target_role_arn #=> String
5659
+ # resp.association.external_id #=> String
5515
5660
  #
5516
5661
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/UpdatePodIdentityAssociation AWS API Documentation
5517
5662
  #
@@ -5540,7 +5685,7 @@ module Aws::EKS
5540
5685
  tracer: tracer
5541
5686
  )
5542
5687
  context[:gem_name] = 'aws-sdk-eks'
5543
- context[:gem_version] = '1.138.0'
5688
+ context[:gem_version] = '1.139.0'
5544
5689
  Seahorse::Client::Request.new(handlers, context)
5545
5690
  end
5546
5691
 
@@ -697,6 +697,8 @@ module Aws::EKS
697
697
  CreatePodIdentityAssociationRequest.add_member(:role_arn, Shapes::ShapeRef.new(shape: String, required: true, location_name: "roleArn"))
698
698
  CreatePodIdentityAssociationRequest.add_member(:client_request_token, Shapes::ShapeRef.new(shape: String, location_name: "clientRequestToken", metadata: {"idempotencyToken" => true}))
699
699
  CreatePodIdentityAssociationRequest.add_member(:tags, Shapes::ShapeRef.new(shape: TagMap, location_name: "tags"))
700
+ CreatePodIdentityAssociationRequest.add_member(:disable_session_tags, Shapes::ShapeRef.new(shape: BoxedBoolean, location_name: "disableSessionTags"))
701
+ CreatePodIdentityAssociationRequest.add_member(:target_role_arn, Shapes::ShapeRef.new(shape: String, location_name: "targetRoleArn"))
700
702
  CreatePodIdentityAssociationRequest.struct_class = Types::CreatePodIdentityAssociationRequest
701
703
 
702
704
  CreatePodIdentityAssociationResponse.add_member(:association, Shapes::ShapeRef.new(shape: PodIdentityAssociation, location_name: "association"))
@@ -1299,6 +1301,9 @@ module Aws::EKS
1299
1301
  PodIdentityAssociation.add_member(:created_at, Shapes::ShapeRef.new(shape: Timestamp, location_name: "createdAt"))
1300
1302
  PodIdentityAssociation.add_member(:modified_at, Shapes::ShapeRef.new(shape: Timestamp, location_name: "modifiedAt"))
1301
1303
  PodIdentityAssociation.add_member(:owner_arn, Shapes::ShapeRef.new(shape: String, location_name: "ownerArn"))
1304
+ PodIdentityAssociation.add_member(:disable_session_tags, Shapes::ShapeRef.new(shape: BoxedBoolean, location_name: "disableSessionTags"))
1305
+ PodIdentityAssociation.add_member(:target_role_arn, Shapes::ShapeRef.new(shape: String, location_name: "targetRoleArn"))
1306
+ PodIdentityAssociation.add_member(:external_id, Shapes::ShapeRef.new(shape: String, location_name: "externalId"))
1302
1307
  PodIdentityAssociation.struct_class = Types::PodIdentityAssociation
1303
1308
 
1304
1309
  PodIdentityAssociationSummaries.member = Shapes::ShapeRef.new(shape: PodIdentityAssociationSummary)
@@ -1524,6 +1529,8 @@ module Aws::EKS
1524
1529
  UpdatePodIdentityAssociationRequest.add_member(:association_id, Shapes::ShapeRef.new(shape: String, required: true, location: "uri", location_name: "associationId"))
1525
1530
  UpdatePodIdentityAssociationRequest.add_member(:role_arn, Shapes::ShapeRef.new(shape: String, location_name: "roleArn"))
1526
1531
  UpdatePodIdentityAssociationRequest.add_member(:client_request_token, Shapes::ShapeRef.new(shape: String, location_name: "clientRequestToken", metadata: {"idempotencyToken" => true}))
1532
+ UpdatePodIdentityAssociationRequest.add_member(:disable_session_tags, Shapes::ShapeRef.new(shape: BoxedBoolean, location_name: "disableSessionTags"))
1533
+ UpdatePodIdentityAssociationRequest.add_member(:target_role_arn, Shapes::ShapeRef.new(shape: String, location_name: "targetRoleArn"))
1527
1534
  UpdatePodIdentityAssociationRequest.struct_class = Types::UpdatePodIdentityAssociationRequest
1528
1535
 
1529
1536
  UpdatePodIdentityAssociationResponse.add_member(:association, Shapes::ShapeRef.new(shape: PodIdentityAssociation, location_name: "association"))
@@ -252,12 +252,12 @@ module Aws::EKS
252
252
  # @return [String]
253
253
  #
254
254
  # @!attribute [rw] pod_identity_associations
255
- # An array of Pod Identity Assocations owned by the Addon. Each EKS
256
- # Pod Identity association maps a role to a service account in a
257
- # namespace in the cluster.
255
+ # An array of EKS Pod Identity associations owned by the add-on. Each
256
+ # association maps a role to a service account in a namespace in the
257
+ # cluster.
258
258
  #
259
259
  # For more information, see [Attach an IAM Role to an Amazon EKS
260
- # add-on using Pod Identity][1] in the *Amazon EKS User Guide*.
260
+ # add-on using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
261
261
  #
262
262
  #
263
263
  #
@@ -388,13 +388,13 @@ module Aws::EKS
388
388
  include Aws::Structure
389
389
  end
390
390
 
391
- # A type of Pod Identity Association owned by an Amazon EKS Add-on.
391
+ # A type of EKS Pod Identity association owned by an Amazon EKS add-on.
392
392
  #
393
- # Each EKS Pod Identity Association maps a role to a service account in
394
- # a namespace in the cluster.
393
+ # Each association maps a role to a service account in a namespace in
394
+ # the cluster.
395
395
  #
396
396
  # For more information, see [Attach an IAM Role to an Amazon EKS add-on
397
- # using Pod Identity][1] in the *Amazon EKS User Guide*.
397
+ # using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
398
398
  #
399
399
  #
400
400
  #
@@ -417,14 +417,14 @@ module Aws::EKS
417
417
  include Aws::Structure
418
418
  end
419
419
 
420
- # Information about how to configure IAM for an Addon.
420
+ # Information about how to configure IAM for an add-on.
421
421
  #
422
422
  # @!attribute [rw] service_account
423
- # The Kubernetes Service Account name used by the addon.
423
+ # The Kubernetes Service Account name used by the add-on.
424
424
  # @return [String]
425
425
  #
426
426
  # @!attribute [rw] recommended_managed_policies
427
- # A suggested IAM Policy for the addon.
427
+ # A suggested IAM Policy for the add-on.
428
428
  # @return [Array<String>]
429
429
  #
430
430
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/AddonPodIdentityConfiguration AWS API Documentation
@@ -447,7 +447,7 @@ module Aws::EKS
447
447
  # @return [Array<String>]
448
448
  #
449
449
  # @!attribute [rw] compute_types
450
- # Indicates the compute type of the addon version.
450
+ # Indicates the compute type of the add-on version.
451
451
  # @return [Array<String>]
452
452
  #
453
453
  # @!attribute [rw] compatibilities
@@ -459,7 +459,7 @@ module Aws::EKS
459
459
  # @return [Boolean]
460
460
  #
461
461
  # @!attribute [rw] requires_iam_permissions
462
- # Indicates if the Addon requires IAM Permissions to operate, such as
462
+ # Indicates if the add-on requires IAM Permissions to operate, such as
463
463
  # networking permissions.
464
464
  # @return [Boolean]
465
465
  #
@@ -1525,12 +1525,11 @@ module Aws::EKS
1525
1525
  # @return [String]
1526
1526
  #
1527
1527
  # @!attribute [rw] pod_identity_associations
1528
- # An array of Pod Identity Assocations to be created. Each EKS Pod
1529
- # Identity association maps a Kubernetes service account to an IAM
1530
- # Role.
1528
+ # An array of EKS Pod Identity associations to be created. Each
1529
+ # association maps a Kubernetes service account to an IAM role.
1531
1530
  #
1532
1531
  # For more information, see [Attach an IAM Role to an Amazon EKS
1533
- # add-on using Pod Identity][1] in the *Amazon EKS User Guide*.
1532
+ # add-on using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
1534
1533
  #
1535
1534
  #
1536
1535
  #
@@ -1680,8 +1679,8 @@ module Aws::EKS
1680
1679
  # If you set this value to `False` when creating a cluster, the
1681
1680
  # default networking add-ons will not be installed.
1682
1681
  #
1683
- # The default networking addons include vpc-cni, coredns, and
1684
- # kube-proxy.
1682
+ # The default networking add-ons include `vpc-cni`, `coredns`, and
1683
+ # `kube-proxy`.
1685
1684
  #
1686
1685
  # Use this option when you plan to install third-party alternative
1687
1686
  # add-ons or self-manage the default networking add-ons.
@@ -2169,13 +2168,14 @@ module Aws::EKS
2169
2168
  end
2170
2169
 
2171
2170
  # @!attribute [rw] cluster_name
2172
- # The name of the cluster to create the association in.
2171
+ # The name of the cluster to create the EKS Pod Identity association
2172
+ # in.
2173
2173
  # @return [String]
2174
2174
  #
2175
2175
  # @!attribute [rw] namespace
2176
2176
  # The name of the Kubernetes namespace inside the cluster to create
2177
- # the association in. The service account and the pods that use the
2178
- # service account must be in this namespace.
2177
+ # the EKS Pod Identity association in. The service account and the
2178
+ # Pods that use the service account must be in this namespace.
2179
2179
  # @return [String]
2180
2180
  #
2181
2181
  # @!attribute [rw] service_account
@@ -2186,7 +2186,7 @@ module Aws::EKS
2186
2186
  # @!attribute [rw] role_arn
2187
2187
  # The Amazon Resource Name (ARN) of the IAM role to associate with the
2188
2188
  # service account. The EKS Pod Identity agent manages credentials to
2189
- # assume this role for applications in the containers in the pods that
2189
+ # assume this role for applications in the containers in the Pods that
2190
2190
  # use this service account.
2191
2191
  # @return [String]
2192
2192
  #
@@ -2230,6 +2230,53 @@ module Aws::EKS
2230
2230
  # against your tags per resource limit.
2231
2231
  # @return [Hash<String,String>]
2232
2232
  #
2233
+ # @!attribute [rw] disable_session_tags
2234
+ # Disable the automatic sessions tags that are appended by EKS Pod
2235
+ # Identity.
2236
+ #
2237
+ # EKS Pod Identity adds a pre-defined set of session tags when it
2238
+ # assumes the role. You can use these tags to author a single role
2239
+ # that can work across resources by allowing access to Amazon Web
2240
+ # Services resources based on matching tags. By default, EKS Pod
2241
+ # Identity attaches six tags, including tags for cluster name,
2242
+ # namespace, and service account name. For the list of tags added by
2243
+ # EKS Pod Identity, see [List of session tags added by EKS Pod
2244
+ # Identity][1] in the *Amazon EKS User Guide*.
2245
+ #
2246
+ # Amazon Web Services compresses inline session policies, managed
2247
+ # policy ARNs, and session tags into a packed binary format that has a
2248
+ # separate limit. If you receive a `PackedPolicyTooLarge` error
2249
+ # indicating the packed binary format has exceeded the size limit, you
2250
+ # can attempt to reduce the size by disabling the session tags added
2251
+ # by EKS Pod Identity.
2252
+ #
2253
+ #
2254
+ #
2255
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-abac.html#pod-id-abac-tags
2256
+ # @return [Boolean]
2257
+ #
2258
+ # @!attribute [rw] target_role_arn
2259
+ # The Amazon Resource Name (ARN) of the target IAM role to associate
2260
+ # with the service account. This role is assumed by using the EKS Pod
2261
+ # Identity association role, then the credentials for this role are
2262
+ # injected into the Pod.
2263
+ #
2264
+ # When you run applications on Amazon EKS, your application might need
2265
+ # to access Amazon Web Services resources from a different role that
2266
+ # exists in the same or different Amazon Web Services account. For
2267
+ # example, your application running in “Account A” might need to
2268
+ # access resources, such as Amazon S3 buckets in “Account B” or within
2269
+ # “Account A” itself. You can create a association to access Amazon
2270
+ # Web Services resources in “Account B” by creating two IAM roles: a
2271
+ # role in “Account A” and a role in “Account B” (which can be the same
2272
+ # or different account), each with the necessary trust and permission
2273
+ # policies. After you provide these roles in the *IAM role* and
2274
+ # *Target IAM role* fields, EKS will perform role chaining to ensure
2275
+ # your application gets the required permissions. This means Role A
2276
+ # will assume Role B, allowing your Pods to securely access resources
2277
+ # like S3 buckets in the target account.
2278
+ # @return [String]
2279
+ #
2233
2280
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/CreatePodIdentityAssociationRequest AWS API Documentation
2234
2281
  #
2235
2282
  class CreatePodIdentityAssociationRequest < Struct.new(
@@ -2238,7 +2285,9 @@ module Aws::EKS
2238
2285
  :service_account,
2239
2286
  :role_arn,
2240
2287
  :client_request_token,
2241
- :tags)
2288
+ :tags,
2289
+ :disable_session_tags,
2290
+ :target_role_arn)
2242
2291
  SENSITIVE = []
2243
2292
  include Aws::Structure
2244
2293
  end
@@ -2593,9 +2642,9 @@ module Aws::EKS
2593
2642
  # @return [String]
2594
2643
  #
2595
2644
  # @!attribute [rw] pod_identity_configuration
2596
- # The Kubernetes service account name used by the addon, and any
2645
+ # The Kubernetes service account name used by the add-on, and any
2597
2646
  # suggested IAM policies. Use this information to create an IAM Role
2598
- # for the Addon.
2647
+ # for the add-on.
2599
2648
  # @return [Array<Types::AddonPodIdentityConfiguration>]
2600
2649
  #
2601
2650
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/DescribeAddonConfigurationResponse AWS API Documentation
@@ -5672,7 +5721,7 @@ module Aws::EKS
5672
5721
  #
5673
5722
  # @!attribute [rw] namespace
5674
5723
  # The name of the Kubernetes namespace inside the cluster to create
5675
- # the association in. The service account and the pods that use the
5724
+ # the association in. The service account and the Pods that use the
5676
5725
  # service account must be in this namespace.
5677
5726
  # @return [String]
5678
5727
  #
@@ -5684,7 +5733,7 @@ module Aws::EKS
5684
5733
  # @!attribute [rw] role_arn
5685
5734
  # The Amazon Resource Name (ARN) of the IAM role to associate with the
5686
5735
  # service account. The EKS Pod Identity agent manages credentials to
5687
- # assume this role for applications in the containers in the pods that
5736
+ # assume this role for applications in the containers in the Pods that
5688
5737
  # use this service account.
5689
5738
  # @return [String]
5690
5739
  #
@@ -5733,12 +5782,55 @@ module Aws::EKS
5733
5782
  # @return [Time]
5734
5783
  #
5735
5784
  # @!attribute [rw] modified_at
5736
- # The most recent timestamp that the association was modified at
5785
+ # The most recent timestamp that the association was modified at.
5737
5786
  # @return [Time]
5738
5787
  #
5739
5788
  # @!attribute [rw] owner_arn
5740
- # If defined, the Pod Identity Association is owned by an Amazon EKS
5741
- # Addon.
5789
+ # If defined, the EKS Pod Identity association is owned by an Amazon
5790
+ # EKS add-on.
5791
+ # @return [String]
5792
+ #
5793
+ # @!attribute [rw] disable_session_tags
5794
+ # The state of the automatic sessions tags. The value of *true*
5795
+ # disables these tags.
5796
+ #
5797
+ # EKS Pod Identity adds a pre-defined set of session tags when it
5798
+ # assumes the role. You can use these tags to author a single role
5799
+ # that can work across resources by allowing access to Amazon Web
5800
+ # Services resources based on matching tags. By default, EKS Pod
5801
+ # Identity attaches six tags, including tags for cluster name,
5802
+ # namespace, and service account name. For the list of tags added by
5803
+ # EKS Pod Identity, see [List of session tags added by EKS Pod
5804
+ # Identity][1] in the *Amazon EKS User Guide*.
5805
+ #
5806
+ #
5807
+ #
5808
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-abac.html#pod-id-abac-tags
5809
+ # @return [Boolean]
5810
+ #
5811
+ # @!attribute [rw] target_role_arn
5812
+ # The Amazon Resource Name (ARN) of the target IAM role to associate
5813
+ # with the service account. This role is assumed by using the EKS Pod
5814
+ # Identity association role, then the credentials for this role are
5815
+ # injected into the Pod.
5816
+ # @return [String]
5817
+ #
5818
+ # @!attribute [rw] external_id
5819
+ # The unique identifier for this EKS Pod Identity association for a
5820
+ # target IAM role. You put this value in the trust policy of the
5821
+ # target role, in a `Condition` to match the `sts.ExternalId`. This
5822
+ # ensures that the target role can only be assumed by this
5823
+ # association. This prevents the *confused deputy problem*. For more
5824
+ # information about the confused deputy problem, see [The confused
5825
+ # deputy problem][1] in the *IAM User Guide*.
5826
+ #
5827
+ # If you want to use the same target role with multiple associations
5828
+ # or other roles, use independent statements in the trust policy to
5829
+ # allow `sts:AssumeRole` access from each role.
5830
+ #
5831
+ #
5832
+ #
5833
+ # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html
5742
5834
  # @return [String]
5743
5835
  #
5744
5836
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/PodIdentityAssociation AWS API Documentation
@@ -5753,7 +5845,10 @@ module Aws::EKS
5753
5845
  :tags,
5754
5846
  :created_at,
5755
5847
  :modified_at,
5756
- :owner_arn)
5848
+ :owner_arn,
5849
+ :disable_session_tags,
5850
+ :target_role_arn,
5851
+ :external_id)
5757
5852
  SENSITIVE = []
5758
5853
  include Aws::Structure
5759
5854
  end
@@ -5782,7 +5877,7 @@ module Aws::EKS
5782
5877
  #
5783
5878
  # @!attribute [rw] namespace
5784
5879
  # The name of the Kubernetes namespace inside the cluster to create
5785
- # the association in. The service account and the pods that use the
5880
+ # the association in. The service account and the Pods that use the
5786
5881
  # service account must be in this namespace.
5787
5882
  # @return [String]
5788
5883
  #
@@ -5800,8 +5895,7 @@ module Aws::EKS
5800
5895
  # @return [String]
5801
5896
  #
5802
5897
  # @!attribute [rw] owner_arn
5803
- # If defined, the Pod Identity Association is owned by an Amazon EKS
5804
- # Addon.
5898
+ # If defined, the association is owned by an Amazon EKS add-on.
5805
5899
  # @return [String]
5806
5900
  #
5807
5901
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/PodIdentityAssociationSummary AWS API Documentation
@@ -5946,7 +6040,7 @@ module Aws::EKS
5946
6040
  # It must satisfy the following requirements:
5947
6041
  #
5948
6042
  # * Each block must be within an `IPv4` RFC-1918 network range.
5949
- # Minimum allowed size is /24, maximum allowed size is /8.
6043
+ # Minimum allowed size is /32, maximum allowed size is /8.
5950
6044
  # Publicly-routable addresses aren't supported.
5951
6045
  #
5952
6046
  # * Each block cannot overlap with the range of the VPC CIDR blocks
@@ -5984,7 +6078,7 @@ module Aws::EKS
5984
6078
  # It must satisfy the following requirements:
5985
6079
  #
5986
6080
  # * Each block must be within an `IPv4` RFC-1918 network range.
5987
- # Minimum allowed size is /24, maximum allowed size is /8.
6081
+ # Minimum allowed size is /32, maximum allowed size is /8.
5988
6082
  # Publicly-routable addresses aren't supported.
5989
6083
  #
5990
6084
  # * Each block cannot overlap with the range of the VPC CIDR blocks
@@ -6034,7 +6128,7 @@ module Aws::EKS
6034
6128
  # It must satisfy the following requirements:
6035
6129
  #
6036
6130
  # * Each block must be within an `IPv4` RFC-1918 network range. Minimum
6037
- # allowed size is /24, maximum allowed size is /8. Publicly-routable
6131
+ # allowed size is /32, maximum allowed size is /8. Publicly-routable
6038
6132
  # addresses aren't supported.
6039
6133
  #
6040
6134
  # * Each block cannot overlap with the range of the VPC CIDR blocks for
@@ -6067,7 +6161,7 @@ module Aws::EKS
6067
6161
  # It must satisfy the following requirements:
6068
6162
  #
6069
6163
  # * Each block must be within an `IPv4` RFC-1918 network range.
6070
- # Minimum allowed size is /24, maximum allowed size is /8.
6164
+ # Minimum allowed size is /32, maximum allowed size is /8.
6071
6165
  # Publicly-routable addresses aren't supported.
6072
6166
  #
6073
6167
  # * Each block cannot overlap with the range of the VPC CIDR blocks
@@ -6112,7 +6206,7 @@ module Aws::EKS
6112
6206
  # It must satisfy the following requirements:
6113
6207
  #
6114
6208
  # * Each block must be within an `IPv4` RFC-1918 network range. Minimum
6115
- # allowed size is /24, maximum allowed size is /8. Publicly-routable
6209
+ # allowed size is /32, maximum allowed size is /8. Publicly-routable
6116
6210
  # addresses aren't supported.
6117
6211
  #
6118
6212
  # * Each block cannot overlap with the range of the VPC CIDR blocks for
@@ -6133,7 +6227,7 @@ module Aws::EKS
6133
6227
  # It must satisfy the following requirements:
6134
6228
  #
6135
6229
  # * Each block must be within an `IPv4` RFC-1918 network range.
6136
- # Minimum allowed size is /24, maximum allowed size is /8.
6230
+ # Minimum allowed size is /32, maximum allowed size is /8.
6137
6231
  # Publicly-routable addresses aren't supported.
6138
6232
  #
6139
6233
  # * Each block cannot overlap with the range of the VPC CIDR blocks
@@ -6686,14 +6780,13 @@ module Aws::EKS
6686
6780
  # @return [String]
6687
6781
  #
6688
6782
  # @!attribute [rw] pod_identity_associations
6689
- # An array of Pod Identity Assocations to be updated. Each EKS Pod
6690
- # Identity association maps a Kubernetes service account to an IAM
6691
- # Role. If this value is left blank, no change. If an empty array is
6692
- # provided, existing Pod Identity Assocations owned by the Addon are
6693
- # deleted.
6783
+ # An array of EKS Pod Identity associations to be updated. Each
6784
+ # association maps a Kubernetes service account to an IAM role. If
6785
+ # this value is left blank, no change. If an empty array is provided,
6786
+ # existing associations owned by the add-on are deleted.
6694
6787
  #
6695
6788
  # For more information, see [Attach an IAM Role to an Amazon EKS
6696
- # add-on using Pod Identity][1] in the *Amazon EKS User Guide*.
6789
+ # add-on using EKS Pod Identity][1] in the *Amazon EKS User Guide*.
6697
6790
  #
6698
6791
  #
6699
6792
  #
@@ -7149,7 +7242,7 @@ module Aws::EKS
7149
7242
  # @return [String]
7150
7243
  #
7151
7244
  # @!attribute [rw] role_arn
7152
- # The new IAM role to change the
7245
+ # The new IAM role to change in the association.
7153
7246
  # @return [String]
7154
7247
  #
7155
7248
  # @!attribute [rw] client_request_token
@@ -7160,20 +7253,68 @@ module Aws::EKS
7160
7253
  # not need to pass this option.
7161
7254
  # @return [String]
7162
7255
  #
7256
+ # @!attribute [rw] disable_session_tags
7257
+ # Disable the automatic sessions tags that are appended by EKS Pod
7258
+ # Identity.
7259
+ #
7260
+ # EKS Pod Identity adds a pre-defined set of session tags when it
7261
+ # assumes the role. You can use these tags to author a single role
7262
+ # that can work across resources by allowing access to Amazon Web
7263
+ # Services resources based on matching tags. By default, EKS Pod
7264
+ # Identity attaches six tags, including tags for cluster name,
7265
+ # namespace, and service account name. For the list of tags added by
7266
+ # EKS Pod Identity, see [List of session tags added by EKS Pod
7267
+ # Identity][1] in the *Amazon EKS User Guide*.
7268
+ #
7269
+ # Amazon Web Services compresses inline session policies, managed
7270
+ # policy ARNs, and session tags into a packed binary format that has a
7271
+ # separate limit. If you receive a `PackedPolicyTooLarge` error
7272
+ # indicating the packed binary format has exceeded the size limit, you
7273
+ # can attempt to reduce the size by disabling the session tags added
7274
+ # by EKS Pod Identity.
7275
+ #
7276
+ #
7277
+ #
7278
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-abac.html#pod-id-abac-tags
7279
+ # @return [Boolean]
7280
+ #
7281
+ # @!attribute [rw] target_role_arn
7282
+ # The Amazon Resource Name (ARN) of the target IAM role to associate
7283
+ # with the service account. This role is assumed by using the EKS Pod
7284
+ # Identity association role, then the credentials for this role are
7285
+ # injected into the Pod.
7286
+ #
7287
+ # When you run applications on Amazon EKS, your application might need
7288
+ # to access Amazon Web Services resources from a different role that
7289
+ # exists in the same or different Amazon Web Services account. For
7290
+ # example, your application running in “Account A” might need to
7291
+ # access resources, such as buckets in “Account B” or within “Account
7292
+ # A” itself. You can create a association to access Amazon Web
7293
+ # Services resources in “Account B” by creating two IAM roles: a role
7294
+ # in “Account A” and a role in “Account B” (which can be the same or
7295
+ # different account), each with the necessary trust and permission
7296
+ # policies. After you provide these roles in the *IAM role* and
7297
+ # *Target IAM role* fields, EKS will perform role chaining to ensure
7298
+ # your application gets the required permissions. This means Role A
7299
+ # will assume Role B, allowing your Pods to securely access resources
7300
+ # like S3 buckets in the target account.
7301
+ # @return [String]
7302
+ #
7163
7303
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/UpdatePodIdentityAssociationRequest AWS API Documentation
7164
7304
  #
7165
7305
  class UpdatePodIdentityAssociationRequest < Struct.new(
7166
7306
  :cluster_name,
7167
7307
  :association_id,
7168
7308
  :role_arn,
7169
- :client_request_token)
7309
+ :client_request_token,
7310
+ :disable_session_tags,
7311
+ :target_role_arn)
7170
7312
  SENSITIVE = []
7171
7313
  include Aws::Structure
7172
7314
  end
7173
7315
 
7174
7316
  # @!attribute [rw] association
7175
- # The full description of the EKS Pod Identity association that was
7176
- # updated.
7317
+ # The full description of the association that was updated.
7177
7318
  # @return [Types::PodIdentityAssociation]
7178
7319
  #
7179
7320
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/UpdatePodIdentityAssociationResponse AWS API Documentation
@@ -7303,8 +7444,10 @@ module Aws::EKS
7303
7444
  # access, your cluster's Kubernetes API server can only receive
7304
7445
  # requests from within the cluster VPC. The default value for this
7305
7446
  # parameter is `true`, which enables public access for your Kubernetes
7306
- # API server. For more information, see [Amazon EKS cluster endpoint
7307
- # access control][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7447
+ # API server. The endpoint domain name and IP address family depends
7448
+ # on the value of the `ipFamily` for the cluster. For more
7449
+ # information, see [Cluster API server endpoint][1] in the <i>
7450
+ # <i>Amazon EKS User Guide</i> </i>.
7308
7451
  #
7309
7452
  #
7310
7453
  #
@@ -7320,8 +7463,8 @@ module Aws::EKS
7320
7463
  # server. If you disable private access and you have nodes or Fargate
7321
7464
  # pods in the cluster, then ensure that `publicAccessCidrs` includes
7322
7465
  # the necessary CIDR blocks for communication with the nodes or
7323
- # Fargate pods. For more information, see [Amazon EKS cluster endpoint
7324
- # access control][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7466
+ # Fargate pods. For more information, see [Cluster API server
7467
+ # endpoint][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7325
7468
  #
7326
7469
  #
7327
7470
  #
@@ -7332,11 +7475,16 @@ module Aws::EKS
7332
7475
  # The CIDR blocks that are allowed access to your cluster's public
7333
7476
  # Kubernetes API server endpoint. Communication to the endpoint from
7334
7477
  # addresses outside of the CIDR blocks that you specify is denied. The
7335
- # default value is `0.0.0.0/0`. If you've disabled private endpoint
7336
- # access, make sure that you specify the necessary CIDR blocks for
7337
- # every node and Fargate `Pod` in the cluster. For more information,
7338
- # see [Amazon EKS cluster endpoint access control][1] in the <i>
7339
- # <i>Amazon EKS User Guide</i> </i>.
7478
+ # default value is `0.0.0.0/0` and additionally `::/0` for dual-stack
7479
+ # `IPv6` clusters. If you've disabled private endpoint access, make
7480
+ # sure that you specify the necessary CIDR blocks for every node and
7481
+ # Fargate `Pod` in the cluster. For more information, see [Cluster API
7482
+ # server endpoint][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7483
+ #
7484
+ # Note that the public endpoints are dual-stack for only `IPv6`
7485
+ # clusters that are made after October 2024. You can't add `IPv6`
7486
+ # CIDR blocks to `IPv4` clusters or `IPv6` clusters that were made
7487
+ # before October 2024.
7340
7488
  #
7341
7489
  #
7342
7490
  #
@@ -7390,9 +7538,8 @@ module Aws::EKS
7390
7538
  # the internet. If this value is disabled and you have nodes or
7391
7539
  # Fargate pods in the cluster, then ensure that `publicAccessCidrs`
7392
7540
  # includes the necessary CIDR blocks for communication with the nodes
7393
- # or Fargate pods. For more information, see [Amazon EKS cluster
7394
- # endpoint access control][1] in the <i> <i>Amazon EKS User Guide</i>
7395
- # </i>.
7541
+ # or Fargate pods. For more information, see [Cluster API server
7542
+ # endpoint][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7396
7543
  #
7397
7544
  #
7398
7545
  #
@@ -7401,7 +7548,22 @@ module Aws::EKS
7401
7548
  #
7402
7549
  # @!attribute [rw] public_access_cidrs
7403
7550
  # The CIDR blocks that are allowed access to your cluster's public
7404
- # Kubernetes API server endpoint.
7551
+ # Kubernetes API server endpoint. Communication to the endpoint from
7552
+ # addresses outside of the CIDR blocks that you specify is denied. The
7553
+ # default value is `0.0.0.0/0` and additionally `::/0` for dual-stack
7554
+ # `IPv6` clusters. If you've disabled private endpoint access, make
7555
+ # sure that you specify the necessary CIDR blocks for every node and
7556
+ # Fargate `Pod` in the cluster. For more information, see [Cluster API
7557
+ # server endpoint][1] in the <i> <i>Amazon EKS User Guide</i> </i>.
7558
+ #
7559
+ # Note that the public endpoints are dual-stack for only `IPv6`
7560
+ # clusters that are made after October 2024. You can't add `IPv6`
7561
+ # CIDR blocks to `IPv4` clusters or `IPv6` clusters that were made
7562
+ # before October 2024.
7563
+ #
7564
+ #
7565
+ #
7566
+ # [1]: https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html
7405
7567
  # @return [Array<String>]
7406
7568
  #
7407
7569
  # @see http://docs.aws.amazon.com/goto/WebAPI/eks-2017-11-01/VpcConfigResponse AWS API Documentation
data/lib/aws-sdk-eks.rb CHANGED
@@ -55,7 +55,7 @@ module Aws::EKS
55
55
  autoload :EndpointProvider, 'aws-sdk-eks/endpoint_provider'
56
56
  autoload :Endpoints, 'aws-sdk-eks/endpoints'
57
57
 
58
- GEM_VERSION = '1.138.0'
58
+ GEM_VERSION = '1.139.0'
59
59
 
60
60
  end
61
61
 
data/sig/client.rbs CHANGED
@@ -362,7 +362,9 @@ module Aws
362
362
  service_account: ::String,
363
363
  role_arn: ::String,
364
364
  ?client_request_token: ::String,
365
- ?tags: Hash[::String, ::String]
365
+ ?tags: Hash[::String, ::String],
366
+ ?disable_session_tags: bool,
367
+ ?target_role_arn: ::String
366
368
  ) -> _CreatePodIdentityAssociationResponseSuccess
367
369
  | (Hash[Symbol, untyped] params, ?Hash[Symbol, untyped] options) -> _CreatePodIdentityAssociationResponseSuccess
368
370
 
@@ -1052,7 +1054,9 @@ module Aws
1052
1054
  cluster_name: ::String,
1053
1055
  association_id: ::String,
1054
1056
  ?role_arn: ::String,
1055
- ?client_request_token: ::String
1057
+ ?client_request_token: ::String,
1058
+ ?disable_session_tags: bool,
1059
+ ?target_role_arn: ::String
1056
1060
  ) -> _UpdatePodIdentityAssociationResponseSuccess
1057
1061
  | (Hash[Symbol, untyped] params, ?Hash[Symbol, untyped] options) -> _UpdatePodIdentityAssociationResponseSuccess
1058
1062
 
data/sig/types.rbs CHANGED
@@ -433,6 +433,8 @@ module Aws::EKS
433
433
  attr_accessor role_arn: ::String
434
434
  attr_accessor client_request_token: ::String
435
435
  attr_accessor tags: ::Hash[::String, ::String]
436
+ attr_accessor disable_session_tags: bool
437
+ attr_accessor target_role_arn: ::String
436
438
  SENSITIVE: []
437
439
  end
438
440
 
@@ -1230,6 +1232,9 @@ module Aws::EKS
1230
1232
  attr_accessor created_at: ::Time
1231
1233
  attr_accessor modified_at: ::Time
1232
1234
  attr_accessor owner_arn: ::String
1235
+ attr_accessor disable_session_tags: bool
1236
+ attr_accessor target_role_arn: ::String
1237
+ attr_accessor external_id: ::String
1233
1238
  SENSITIVE: []
1234
1239
  end
1235
1240
 
@@ -1524,6 +1529,8 @@ module Aws::EKS
1524
1529
  attr_accessor association_id: ::String
1525
1530
  attr_accessor role_arn: ::String
1526
1531
  attr_accessor client_request_token: ::String
1532
+ attr_accessor disable_session_tags: bool
1533
+ attr_accessor target_role_arn: ::String
1527
1534
  SENSITIVE: []
1528
1535
  end
1529
1536
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-eks
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.138.0
4
+ version: 1.139.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services