Binding EIP
-
It can be used to bind EIP to any BLB instance or BCC instance. -
Only EIPs in the available state support binding operations. -
The bound instance cannot have any existing EIP binding relationship. -
The bound instance cannot be in arrears.
PUT /v{version}/eip/{eip}? {action}&clientToken={clientToken} HTTP/1.1 Host: eip.bj.baidubce.com Authorization: authorization string { "instanceType": instanceType, "instanceId": instanceId }
|
|
|
|
|
---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When the EIP binds the elastic network card or BCC, it binds the primary IP of the elastic network card or the primary IP of the primary network card in the bcc by default. When it needs to bind the secondary IP of the elastic network card or the secondary IP of the primary network card in the bcc, the specific IP to be bound can be assigned in instanceIp
PUT /v1/eip/180.76.122.3? bind&clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1 HOST eip.bj.baidubce.com Authorization bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2016-04-10T08:26:52Z/1800/host; x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02 { "instanceType": "BCC", "instanceId": "i-Tkjq337f" }
PUT /v1/eip/180.76.122.3? bind&clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1 HOST eip.bj.baidubce.com Authorization bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2016-06-21T08:26:52Z/1800/host; x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02 { "instanceType": "BLB", "instanceId": "lb-3ytqlktb" }
PUT /v1/eip/2400:da00:e003:2078:0:3:0:1ed? bind&clientToken=a7e580a2-79d7-4203-9c31-a68a1cf7d108 HTTP/1.1 HOST eip.bj.baidubce.com Authorization bce-auth-v1/08e28f03ea9b11eea8a715135d6be69f/2024-03-25T12:31:26Z/3600/host; x-bce-date/d04aa904d61c452565af7471510f1f1d03f0d7ede2a1bb55eff60b5c6d94211a { "instanceType": "BCC", "instanceId": "i-1GPwA4Iy", "instanceIp": "2400:da00:e003:0:27c:c00:0:5" }
HTTP/1.1 200 OK x-bce-request-id: 946002ee-cb4f-4aad-b686-5be55df27f09 Date: Wed, 10 Apr 2016 08:26:52 GMT Transfer-Encoding: chunked Content-Type: application/json; charset=UTF-8 Server: BWS