DeleteCluster
Deletes an Amazon EKS cluster control plane.
If you have active services in your cluster that are associated with a load balancer, you must delete those services before deleting the cluster so that the load balancers are deleted properly. Otherwise, you can have orphaned resources in your VPC that prevent you from being able to delete the VPC. For more information, see Deleting a cluster in the Amazon EKS User Guide.
If you have managed node groups or Fargate profiles attached to the
cluster, you must delete them first. For more information, see
DeleteNodgroup
and DeleteFargateProfile
.
Request Syntax
DELETE /clusters/name
HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- name
-
The name of the cluster to delete.
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"cluster": {
"accessConfig": {
"authenticationMode": "string",
"bootstrapClusterCreatorAdminPermissions": boolean
},
"arn": "string",
"certificateAuthority": {
"data": "string"
},
"clientRequestToken": "string",
"computeConfig": {
"enabled": boolean,
"nodePools": [ "string" ],
"nodeRoleArn": "string"
},
"connectorConfig": {
"activationCode": "string",
"activationExpiry": number,
"activationId": "string",
"provider": "string",
"roleArn": "string"
},
"createdAt": number,
"encryptionConfig": [
{
"provider": {
"keyArn": "string"
},
"resources": [ "string" ]
}
],
"endpoint": "string",
"health": {
"issues": [
{
"code": "string",
"message": "string",
"resourceIds": [ "string" ]
}
]
},
"id": "string",
"identity": {
"oidc": {
"issuer": "string"
}
},
"kubernetesNetworkConfig": {
"elasticLoadBalancing": {
"enabled": boolean
},
"ipFamily": "string",
"serviceIpv4Cidr": "string",
"serviceIpv6Cidr": "string"
},
"logging": {
"clusterLogging": [
{
"enabled": boolean,
"types": [ "string" ]
}
]
},
"name": "string",
"outpostConfig": {
"controlPlaneInstanceType": "string",
"controlPlanePlacement": {
"groupName": "string"
},
"outpostArns": [ "string" ]
},
"platformVersion": "string",
"remoteNetworkConfig": {
"remoteNodeNetworks": [
{
"cidrs": [ "string" ]
}
],
"remotePodNetworks": [
{
"cidrs": [ "string" ]
}
]
},
"resourcesVpcConfig": {
"clusterSecurityGroupId": "string",
"endpointPrivateAccess": boolean,
"endpointPublicAccess": boolean,
"publicAccessCidrs": [ "string" ],
"securityGroupIds": [ "string" ],
"subnetIds": [ "string" ],
"vpcId": "string"
},
"roleArn": "string",
"status": "string",
"storageConfig": {
"blockStorage": {
"enabled": boolean
}
},
"tags": {
"string" : "string"
},
"upgradePolicy": {
"supportType": "string"
},
"version": "string",
"zonalShiftConfig": {
"enabled": boolean
}
}
}
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.
Errors
For information about the errors that are common to all actions, see Common Errors.
- ClientException
-
These errors are usually caused by a client action. Actions can include using an action or resource on behalf of an IAM principal that doesn't have permissions to use the action or resource or specifying an identifier that is not valid.
HTTP Status Code: 400
- ResourceInUseException
-
The specified resource is in use.
HTTP Status Code: 409
- ResourceNotFoundException
-
The specified resource could not be found. You can view your available clusters with
ListClusters
. You can view your available managed node groups withListNodegroups
. Amazon EKS clusters and node groups are AWS Region specific.HTTP Status Code: 404
- ServerException
-
These errors are usually caused by a server-side issue.
HTTP Status Code: 500
- ServiceUnavailableException
-
The service is unavailable. Back off and retry the operation.
HTTP Status Code: 503
Examples
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 Amazon EKS General
Reference.
You need to learn how to sign HTTP requests only if you intend to manually
create them. When you use the AWS Command Line
Interface (AWS CLI)
Example
The following example deletes a cluster called my-cluster
.
Sample Request
DELETE /clusters/my-cluster HTTP/1.1
Host: eks.us-west-2.amazonaws.com
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: 20180531T231840Z
Authorization: AUTHPARAMS
Sample Response
HTTP/1.1 200 OK
Date: Thu, 31 May 2018 23:18:41 GMT
Content-Type: application/json
Content-Length: 1895
x-amzn-RequestId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
x-amz-apigw-id: HxlgjH_rPHcF7ag=
X-Amzn-Trace-Id: Root=1-xxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx
Connection: keep-alive
{
"cluster": {
"name": "dev",
"arn": "arn:aws:eks:us-west-2:012345678910:cluster/my-cluster",
"createdAt": 1573244832.203,
"version": "1.14",
"endpoint": "https://A0DCCD80A04F01705DD065655C30CC3D.yl4.us-west-2.eks.amazonaws.com",
"roleArn": "arn:aws:iam::012345678910:role/eksClusterRole",
"resourcesVpcConfig": {
"subnetIds": [
"subnet-xxxxxxxxxxxxxxxxx",
"subnet-yyyyyyyyyyyyyyyyy",
"subnet-zzzzzzzzzzzzzzzzz"
],
"securityGroupIds": [
"sg-xxxxxxxxxxxxxxxxx"
],
"clusterSecurityGroupId": "sg-yyyyyyyyyyyyyyyyy",
"vpcId": "vpc-xxxxxxxxxxxxxxxxx",
"endpointPublicAccess": true,
"endpointPrivateAccess": false
},
"logging": {
"clusterLogging": [
{
"types": [
"api",
"audit",
"authenticator",
"controllerManager",
"scheduler"
],
"enabled": false
}
]
},
"identity": {
"oidc": {
"issuer": "https://oidc.eks.us-west-2.amazonaws.com/id/XXXXXXXXXXXXX097E4AC3A07B6B79B9C"
}
},
"status": "DELETING",
"certificateAuthority": {
"data": "HERE_BE_SOME_CERT_DATA==="
},
"platformVersion": "eks.3",
"tags": {}
}
}
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: