Module aws_sdk_eks::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Elastic Kubernetes Service can respond with.

Structs

• Addon

  An Amazon EKS add-on. For more information, see Amazon EKS add-ons in the Amazon EKS User Guide.

• AddonHealth

  The health of the add-on.

• AddonInfo

  Information about an add-on.

• AddonIssue

  An issue related to an add-on.

• AddonVersionInfo

  Information about an add-on version.

• AutoScalingGroup

  An Auto Scaling group that is associated with an Amazon EKS managed node group.

• Certificate

  An object representing the certificate-authority-data for your cluster.

• Cluster

  An object representing an Amazon EKS cluster.

• ClusterHealth

  An object representing the health of your local Amazon EKS cluster on an Amazon Web Services Outpost. You can't use this API with an Amazon EKS cluster on the Amazon Web Services cloud.

• ClusterIssue

  An issue with your local Amazon EKS cluster on an Amazon Web Services Outpost. You can't use this API with an Amazon EKS cluster on the Amazon Web Services cloud.

• Compatibility

  Compatibility information.

• ConnectorConfigRequest

  The configuration sent to a cluster for configuration.

• ConnectorConfigResponse

  The full description of your connected cluster.

• ControlPlanePlacementRequest

  The placement configuration for all the control plane instances of your local Amazon EKS cluster on an Amazon Web Services Outpost. For more information, see Capacity considerations in the Amazon EKS User Guide.

• ControlPlanePlacementResponse

  The placement configuration for all the control plane instances of your local Amazon EKS cluster on an Amazon Web Services Outpost. For more information, see Capacity considerations in the Amazon EKS User Guide.

• EksAnywhereSubscription

  An EKS Anywhere subscription authorizing the customer to support for licensed clusters and access to EKS Anywhere Curated Packages.

• EksAnywhereSubscriptionTerm

  An object representing the term duration and term unit type of your subscription. This determines the term length of your subscription. Valid values are MONTHS for term unit and 12 or 36 for term duration, indicating a 12 month or 36 month subscription.

• EncryptionConfig

  The encryption configuration for the cluster.

• ErrorDetail

  An object representing an error when an asynchronous operation fails.

• FargateProfile

  An object representing an Fargate profile.

• FargateProfileSelector

  An object representing an Fargate profile selector.

• Identity

  An object representing an identity provider.

• IdentityProviderConfig

  An object representing an identity provider configuration.

• IdentityProviderConfigResponse

  The full description of your identity configuration.

• Issue

  An object representing an issue with an Amazon EKS resource.

• KubernetesNetworkConfigRequest

  The Kubernetes network configuration for the cluster.

• KubernetesNetworkConfigResponse

  The Kubernetes network configuration for the cluster. The response contains a value for serviceIpv6Cidr or serviceIpv4Cidr, but not both.

• LaunchTemplateSpecification

  An object representing a node group launch template specification. The launch template can't include SubnetId , IamInstanceProfile , RequestSpotInstances , HibernationOptions , or TerminateInstances , or the node group deployment or update will fail. For more information about launch templates, see CreateLaunchTemplate in the Amazon EC2 API Reference. For more information about using launch templates with Amazon EKS, see Launch template support in the Amazon EKS User Guide.

• LogSetup

  An object representing the enabled or disabled Kubernetes control plane logs for your cluster.

• Logging

  An object representing the logging configuration for resources in your cluster.

• MarketplaceInformation

  Information about an Amazon EKS add-on from the Amazon Web Services Marketplace.

• Nodegroup

  An object representing an Amazon EKS managed node group.

• NodegroupHealth

  An object representing the health status of the node group.

• NodegroupResources

  An object representing the resources associated with the node group, such as Auto Scaling groups and security groups for remote access.

• NodegroupScalingConfig

  An object representing the scaling configuration details for the Auto Scaling group that is associated with your node group. When creating a node group, you must specify all or none of the properties. When updating a node group, you can specify any or none of the properties.

• NodegroupUpdateConfig

  The node group update configuration.

• Oidc

  An object representing the OpenID Connect (OIDC) identity provider information for the cluster.

• OidcIdentityProviderConfig

  An object representing the configuration for an OpenID Connect (OIDC) identity provider.

• OidcIdentityProviderConfigRequest

  An object representing an OpenID Connect (OIDC) configuration. Before associating an OIDC identity provider to your cluster, review the considerations in Authenticating users for your cluster from an OpenID Connect identity provider in the Amazon EKS User Guide.

• OutpostConfigRequest

  The configuration of your local Amazon EKS cluster on an Amazon Web Services Outpost. Before creating a cluster on an Outpost, review Creating a local cluster on an Outpost in the Amazon EKS User Guide. This API isn't available for Amazon EKS clusters on the Amazon Web Services cloud.

• OutpostConfigResponse

  An object representing the configuration of your local Amazon EKS cluster on an Amazon Web Services Outpost. This API isn't available for Amazon EKS clusters on the Amazon Web Services cloud.

• PodIdentityAssociation

  Amazon EKS Pod Identity associations provide the ability to manage credentials for your applications, similar to the way that 7EC2l instance profiles provide credentials to Amazon EC2 instances.

• PodIdentityAssociationSummary

  The summarized description of the association.

• Provider

  Identifies the Key Management Service (KMS) key used to encrypt the secrets.

• RemoteAccessConfig

  An object representing the remote access configuration for the managed node group.

• Taint

  A property that allows a node to repel a set of pods. For more information, see Node taints on managed node groups.

• Update

  An object representing an asynchronous update.

• UpdateLabelsPayload

  An object representing a Kubernetes label change for a managed node group.

• UpdateParam

  An object representing the details of an update request.

• UpdateTaintsPayload

  An object representing the details of an update to a taints payload. For more information, see Node taints on managed node groups.

• VpcConfigRequest

  An object representing the VPC configuration to use for an Amazon EKS cluster.

• VpcConfigResponse

  An object representing an Amazon EKS cluster VPC configuration response.

Enums

• AddonIssueCode
  When writing a match expression against AddonIssueCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AddonStatus
  When writing a match expression against AddonStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AmiTypes
  When writing a match expression against AmiTypes, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• CapacityTypes
  When writing a match expression against CapacityTypes, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ClusterIssueCode
  When writing a match expression against ClusterIssueCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ClusterStatus
  When writing a match expression against ClusterStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigStatus
  When writing a match expression against ConfigStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConnectorConfigProvider
  When writing a match expression against ConnectorConfigProvider, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EksAnywhereSubscriptionLicenseType
  When writing a match expression against EksAnywhereSubscriptionLicenseType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EksAnywhereSubscriptionStatus
  When writing a match expression against EksAnywhereSubscriptionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EksAnywhereSubscriptionTermUnit
  When writing a match expression against EksAnywhereSubscriptionTermUnit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ErrorCode
  When writing a match expression against ErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FargateProfileStatus
  When writing a match expression against FargateProfileStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• IpFamily
  When writing a match expression against IpFamily, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LogType
  When writing a match expression against LogType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NodegroupIssueCode
  When writing a match expression against NodegroupIssueCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NodegroupStatus
  When writing a match expression against NodegroupStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResolveConflicts
  When writing a match expression against ResolveConflicts, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TaintEffect
  When writing a match expression against TaintEffect, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• UpdateParamType
  When writing a match expression against UpdateParamType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• UpdateStatus
  When writing a match expression against UpdateStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• UpdateType
  When writing a match expression against UpdateType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.