DeleteComputeNodeGroup
Deletes a compute node group. You must delete all queues associated with the compute node group first.
Request Syntax
{
"clientToken": "string",
"clusterIdentifier": "string",
"computeNodeGroupIdentifier": "string"
}Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- clientToken
-
A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. Idempotency ensures that an API request completes only once. With an idempotent request, if the original request completes successfully, the subsequent retries with the same client token return the result from the original successful request and they have no additional effect. If you don't specify a client token, the AWS CLI and SDK automatically generate 1 for you.
Type: String
Length Constraints: Minimum length of 8. Maximum length of 100.
Required: No
- clusterIdentifier
-
The name or ID of the cluster of the compute node group.
Type: String
Pattern:
(pcs_[a-zA-Z0-9]+|[A-Za-z][A-Za-z0-9-]{3,40})Required: Yes
- computeNodeGroupIdentifier
-
The name or ID of the compute node group to delete.
Type: String
Pattern:
(pcs_[a-zA-Z0-9]+|[A-Za-z][A-Za-z0-9-]{3,25})Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
You don't have permission to perform the action.
Examples
-
The launch template instance profile doesn't pass
iam:PassRoleverification. -
There is a mismatch between the account ID and cluster ID.
-
The cluster ID doesn't exist.
-
The EC2 instance isn't present.
HTTP Status Code: 400
-
- ConflictException
-
Your request has conflicting operations. This can occur if you're trying to perform more than 1 operation on the same resource at the same time.
Examples
-
A cluster with the same name already exists.
-
A cluster isn't in
ACTIVEstatus. -
A cluster to delete is in an unstable state. For example, because it still has
ACTIVEnode groups or queues. -
A queue already exists in a cluster.
HTTP Status Code: 400
-
- InternalServerException
-
AWS PCS can't process your request right now. Try again later.
HTTP Status Code: 500
- ResourceNotFoundException
-
The requested resource can't be found. The cluster, node group, or queue you're attempting to get, update, list, or delete doesn't exist.
Examples
HTTP Status Code: 400
- ThrottlingException
-
Your request exceeded a request rate quota. Check the resource's request rate quota and try again.
HTTP Status Code: 400
- ValidationException
-
The request isn't valid.
Examples
-
Your request contains malformed JSON or unsupported characters.
-
The scheduler version isn't supported.
-
There are networking related errors, such as network validation failure.
-
AMI type is
CUSTOMand the launch template doesn't define the AMI ID, or the AMI type is AL2 and the launch template defines the AMI.
HTTP Status Code: 400
-
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
