Modify instance attributes
Updated at：2025-10-20
This API is used to modify the attributes of a specified BCC instance, currently supporting only modification of the instance name or network interface card queue count;
- When modifying the instance name, this API can only be called for instances in the Running or Stopped status; otherwise, a 409 error will be returned;
- When modifying the network interface card queue count of an instance, this API can only be called for instances that are stopped and not in the status of no charge for stopped instances;
- Elastic bare metal (EBC) instances do not support modification of the network interface card queue count;
- The modified network interface card queue count of the instance must not exceed the maximum network interface card queue count supported by the instance specification. The nominal and maximum network interface card queue counts for the instance specification can be queried through the Query Instance Package Specification API.
Request structure
Plain Text
1PUT /v{version}/instance/{instanceId}?{action} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4
5{
6 "name": InstanceName,
7 "netEthQueueCount": newNetEthQueueCount
8}Request headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number |
| instanceId | String | Yes | URL parameter | Specified instance ID |
| action | String | Yes | Query | The action performed on the instance, current value: modifyAttribute. |
| name | String | No | Request Body parameters | Instance name, supporting uppercase and lowercase letters, numbers and special characters-_ /. It must start with a letter and have a length of1 - 65 characters. |
| netEthQueueCount | Integer | No | Request Body parameters | Modified network interface card queue count |
| enableJumboFrame | boolean | No | Request Body parameters | Enable or disable Jumbo frames. Enable: true; Disable: false. Note: Jumbo frames can only be enabled for packages that support this feature. |
Response headers
No special headers are required beyond the standard ones.
Response parameters
There are no special response parameters
Error codes
| Error code | Error description | HTTP status code | Chinese explanation |
|---|---|---|---|
| BadRequest | Bad request parameters or illegal request. | 400 | Invalid request parameters |
| Instance.NameInvalid | Instance name is invalid. | 400 | Invalid name |
| NoSuchObject | The specified object is not found or resource do not exist. | 404 | Resource does not exist |
| OperationDenied | Operation not available. | 409 | Operation not allowed |
Request example
Plain Text
1PUT /v2/instance/i-YufwpQAe?modifyAttribute HTTP/1.1
2Host: bcc.bj.baidubce.com
3ContentType: application/json
4Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
5
6{
7 "name": "new_instance_name",
8 "netEthQueueCount": 3
9}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Wed, 03 Dec 2014 06:42:19 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS