AttachNetworkInterface

Description

When you call this operation, take note of the following items:

• The ENI must be in the Available (Available) state. Each ENI can be bound to a single instance.
• The instance must be in the Running (Running) or Stopped (Stopped) state. When you bind ENIs to instances of some instance types, the instances must be in the Stopped (Stopped) state. For more information, see the "Instance types of the ECS instances that must be in the Stopped (Stopped) state" section in Bind an ENI.

  Note If the last start time of the instance (including the last start time of the instance if it is newly purchased, the last restart time of the instance, and the last reactivation time of the instance) is before April 1, 2018 and the instance stays in the Running state, you must call the RebootInstance operation to restart the instance. Otherwise, the ENI cannot be bound to the instance.
• You can bind multiple ENIs to a single instance. For more information, see ENI overview.
• The instance must be in the same zone and the same VPC as the vSwitch to which the ENI is connected.

Request parameters

Response parameters

Examples

Sample requests

https://ecs.aliyuncs.com/?Action=AttachNetworkInterface
&RegionId=cn-hangzhou
&InstanceId=i-bp16qstyvxj9gpqw****
&NetworkInterfaceId=eni-bp17pdijfczax1huji****
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<AttachNetworkInterfaceResponse>
    <RequestId>473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E</RequestId>
</AttachNetworkInterfaceResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E"
}

Error codes

For a list of error codes, visit the API Error Center.