We are excited to announce our new API Documentation.
Rest
...__namedParameters: [] | [EKSClientConfig]Readonly
configThe resolved configuration of EKSClient class. This is resolved and normalized from the constructor configuration interface.
Optional
options: HttpHandlerOptionsOptional
data: AssociateEncryptionConfigCommandOutputOptional
data: AssociateEncryptionConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: AssociateIdentityProviderConfigCommandOutputOptional
data: AssociateIdentityProviderConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CreateAddonCommandOutputOptional
data: CreateAddonCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CreateClusterCommandOutputOptional
data: CreateClusterCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CreateFargateProfileCommandOutputOptional
data: CreateFargateProfileCommandOutputOptional
options: HttpHandlerOptionsOptional
data: CreateNodegroupCommandOutputOptional
data: CreateNodegroupCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteAddonCommandOutputOptional
data: DeleteAddonCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteClusterCommandOutputOptional
data: DeleteClusterCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteFargateProfileCommandOutputOptional
data: DeleteFargateProfileCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeleteNodegroupCommandOutputOptional
data: DeleteNodegroupCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DeregisterClusterCommandOutputOptional
data: DeregisterClusterCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeAddonCommandOutputOptional
data: DescribeAddonCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeAddonConfigurationCommandOutputOptional
data: DescribeAddonConfigurationCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeAddonVersionsCommandOutputOptional
data: DescribeAddonVersionsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeClusterCommandOutputOptional
data: DescribeClusterCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeFargateProfileCommandOutputOptional
data: DescribeFargateProfileCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeIdentityProviderConfigCommandOutputOptional
data: DescribeIdentityProviderConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeNodegroupCommandOutputOptional
data: DescribeNodegroupCommandOutputOptional
options: HttpHandlerOptionsOptional
data: DescribeUpdateCommandOutputOptional
data: DescribeUpdateCommandOutputDestroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.
Optional
options: HttpHandlerOptionsOptional
data: DisassociateIdentityProviderConfigCommandOutputOptional
data: DisassociateIdentityProviderConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListAddonsCommandOutputOptional
data: ListAddonsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListClustersCommandOutputOptional
data: ListClustersCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListFargateProfilesCommandOutputOptional
data: ListFargateProfilesCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListIdentityProviderConfigsCommandOutputOptional
data: ListIdentityProviderConfigsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListNodegroupsCommandOutputOptional
data: ListNodegroupsCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListTagsForResourceCommandOutputOptional
data: ListTagsForResourceCommandOutputOptional
options: HttpHandlerOptionsOptional
data: ListUpdatesCommandOutputOptional
data: ListUpdatesCommandOutputOptional
options: HttpHandlerOptionsOptional
data: RegisterClusterCommandOutputOptional
data: RegisterClusterCommandOutputOptional
options: HttpHandlerOptionsOptional
data: TagResourceCommandOutputOptional
data: TagResourceCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UntagResourceCommandOutputOptional
data: UntagResourceCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateAddonCommandOutputOptional
data: UpdateAddonCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateClusterConfigCommandOutputOptional
data: UpdateClusterConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateClusterVersionCommandOutputOptional
data: UpdateClusterVersionCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateNodegroupConfigCommandOutputOptional
data: UpdateNodegroupConfigCommandOutputOptional
options: HttpHandlerOptionsOptional
data: UpdateNodegroupVersionCommandOutputOptional
data: UpdateNodegroupVersionCommandOutput
Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on Amazon Web Services without needing to stand up or maintain your own Kubernetes control plane. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications.
Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS are fully compatible with applications running on any standard Kubernetes environment, whether running in on-premises data centers or public clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS without any code modification required.