Elastic Network Interface Mounts Cloud Product Instance
Updated at：2025-10-16
Description
Attach the elastic network interface to the designated cloud product instance. Currently supported instances include cloud hosts and HPAS instances.
- Multiple elastic network interfaces can be bound to a cloud product instance, but only one primary network interface card can be bound to a cloud product instance;
- An elastic network interface can only be bound to one cloud service instance at a time
- Elastic network interfaces can only be bound to cloud product instances in running or stopped status
- The elastic network interface and the cloud product instance to which it is bound must be in the same virtual private cloud, and the availability zones of their respective subnets must be the same
Request structure
Plain Text
1PUT /v{version}/eni/{eniId}?{action}?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "instanceId":{instanceId},
6 "instanceType":{instanceType}
7}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 | For API version No., the current value is 1 |
| eniId | String | Yes | URL parameter | Elastic network interface ID |
| action | String | Yes | Query | The value for this API is attach |
| instanceId | String | Yes | RequestBody | ID of the bound cloud product instance |
| instanceType | String | No | RequestBody | Type of the bound cloud product instance, with current value range being server/hpas, representing cloud host/HPAS respectively, defaulted as server |
| clientToken | String | No | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits. For details, refer to [ClientToken Idempotence Support](VPC/API Reference/General Description.md#Idempotence). |
Response headers
No special headers are required beyond the standard ones.
Response parameters
No special response parameters are available.
Request example
Plain Text
1PUT /v1/eni/eni-w2d4kgc3x0y1?attach&clientToken=cecad37a-5a1e-4135-a1bc-b1a105d12dec HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2017-03-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4{
5 "instanceId":"i-syGfPUYO",
6 "instanceType": "server"
7}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 7e789a40-adac-414a-8bd4-916d6be61112
3Date: Mon, 02 Apr 2019 08:14:25 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS