Amazon Elastic Container Service for Kubernetes
API Reference (API Version 2017-11-01)


Returns descriptive information about an Amazon EKS cluster.

The API server endpoint and certificate authority data returned by this operation are required for kubelet and kubectl to communicate with your Kubernetes API server. For more information, see Create a kubeconfig for Amazon EKS.


The API server endpoint and certificate authority data are not available until the cluster reaches the ACTIVE state.

Request Syntax

GET /clusters/name HTTP/1.1

URI Request Parameters

The request requires the following URI parameters.


The name of the cluster to describe.

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 Content-type: application/json { "cluster": { "arn": "string", "certificateAuthority": { "data": "string" }, "clientRequestToken": "string", "createdAt": number, "endpoint": "string", "name": "string", "platformVersion": "string", "resourcesVpcConfig": { "securityGroupIds": [ "string" ], "subnetIds": [ "string" ], "vpcId": "string" }, "roleArn": "string", "status": "string", "version": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


The full description of your specified cluster.

Type: Cluster object


For information about the errors that are common to all actions, see Common Errors.


These errors are usually caused by a client action, such as using an action or resource on behalf of a user that doesn't have permissions to use the action or resource, or specifying an identifier that is not valid.

HTTP Status Code: 400


The specified resource could not be found. You can view your available clusters with ListClusters. Amazon EKS clusters are Region-specific.

HTTP Status Code: 404


These errors are usually caused by a server-side issue.

HTTP Status Code: 500


The service is unavailable. Back off and retry the operation.

HTTP Status Code: 503


In the following example or examples, the Authorization header contents (AUTHPARAMS) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.


The following example describes a cluster called prod.

Sample Request

GET /clusters/devel HTTP/1.1 Host: Accept-Encoding: identity User-Agent: aws-cli/1.15.0 Python/3.6.5 Darwin/16.7.0 botocore/1.10.0 X-Amz-Date: 20180531T231432Z Authorization: AUTHPARAMS

Sample Response

HTTP/1.1 200 OK Date: Thu, 31 May 2018 23:14:33 GMT Content-Type: application/json Content-Length: 1893 x-amzn-RequestId: 60a0fb5d-6528-11e8-9390-a9f201b334e2 x-amz-apigw-id: Hxk55FMJPHcF8gQ= X-Amzn-Trace-Id: Root=1-5b1081d8-a378ea58d72e0864c39b9ae4 Connection: keep-alive { "cluster": { "endpoint": "", "status": "ACTIVE", "createdAt": 1527807879.988, "certificateAuthority": { "data": "HERE_BE_SOME_CERT_DATA=" }, "arn": "arn:aws:eks:us-west-2:012345678910:cluster/devel", "roleArn": "arn:aws:iam::012345678910:role/eks-service-role-AWSServiceRoleForAmazonEKS-J7ONKE3BQ4PI", "clientRequestToken": null, "version": "1.10", "name": "devel", "resourcesVpcConfig": { "securityGroupIds": [ "sg-6979fe18" ], "vpcId": "vpc-950809ec", "subnetIds": [ "subnet-6782e71e", "subnet-e7e761ac" ] } } }

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: