All Products
Search
Document Center

:AttachNodes

Last Updated:Jan 14, 2026

Adds Elastic Compute Service (ECS) instances as compute nodes to Elastic High Performance Computing (E-HPC) clusters.

Operation description

The ECS instances must meet the following requirements:

  • The ECS instances do not belong to any E-HPC cluster.
  • The ECS instances reside in the same virtual private cloud (VPC) as the cluster.
  • The ECS instances are in the Stopped state.

Take of the following limits:

  • You can specify multiple instance IDs to add them at a time. However, the instances must be of the same type.
  • When an instance is added to the cluster, the system disk is reset by using the image specified by the input parameters.
  • If the instance has data disks, they are not automatically created and mounted after the instance is added.
  • The hostname of the instance remains the same. Therefore, you must ensure that the hostname of the instance to be added is different from the hostname of an existing node in the cluster.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
ehpc:AttachNodesupdate
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ClusterIdstringYes

The ID of the cluster.

ehpc-hz-xxxxxxx
QueueNamestringNo

The name of the queue to which the instance is to be added.

comp
ComputeNodeobjectYes

The list of compute nodes.

InstanceIdsarrayYes

The IDs of ECS instances.

stringNo

The instance ID.

i-xxxxxxxx
ImageIdstringYes

The image ID. This image will be used to replace the original system disk image.

m-bp1h765oyqyxxxxxxxxx

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

RequestIdstring

The request ID.

2263XXXX-XXXX-XXXX-XXXX-XXXX2448XXXX
Successboolean

Indicates whether the request was successful.

Valid values:

  • true
  • false
true

Examples

Sample success responses

JSONformat

{
  "RequestId": "2263XXXX-XXXX-XXXX-XXXX-XXXX2448XXXX",
  "Success": true
}

Error codes

HTTP status codeError codeError messageDescription
403InvalidParamsInvalid parameters: %s.Parameter error.
404ClusterNotFoundThe specified cluster does not exist.The specified instance does not exist.
406DbErrorA database error occurred.A database error occurred.
406EcsErrorAn error occurred while calling the ECS API operation.ECS API call error. %s

For a list of error codes, visit the Service error codes.