Bind EIP
Last Updated：2020-07-20
Description
The EIP is bound to the NAT gateway.
- If the EIP has been bound to EIP, it may be bound only after being unbound.
- If the shared bandwidth has been bound to the NAT, other IPs in the shared bandwidth can continue to be bound.
Request Structure
PUT /v{version}/nat/{natId}?{action}&clientToken={clientToken} HTTP/1.1
Host: bcc.bj.baidubce.com
Authorization: authorization string
{ "eips":[eips] } Request Parameter
| Parameter name | Type | Required or not | Parameter position | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number (the current value is 1) |
| natId | String | Yes | URL parameter | The EIP is bound to the NAT gateway ID. |
| action | String | Yes | Query parameter | For the actions executed by the NAT gateway, the value taken in the interface is bind. |
| clientToken | String | No | Query parameter | Idempotence Token is an ASCII string with length not exceeding 64 bytes, for details, please see ClientToken Idempotence |
| eips | List |
Yes | RequestBody parameter | List of bound EIP IDs For EIPs, only one EIP can be bound, and for the shared bandwidth, and multiple IPs in it can be bound. |
Return Header
There are no other special headers except the public headers.
Return Parameter
There is no special return parameter.
Request Example
PUT /v1/nat/nat-b7ze574srr4g?bind&clientToken={ac31ef8c-5e41-4k38-9ds0-9de700ds5b20} HTTP/1.1
host: bcc.bj.baidubce.com
content-type: application/json
authorization: bce-auth-v1/2830b179831d11e8be57233b1de1e808/2018-07-09T02:11:00Z/3600/host;x-bce-account;x-bce-client-ip;x -bce-date;x-bce-request-id;x-bce-security-token/241df034
75c8a723f7acd63851b343c8a37e654d001e79695e87c83595ca58fd
connection: Keep-Alive
{
"eips" : [ "180.76.186.174" ]
} Return Example
HTTP/1.1 200 OK
x-bce-request-id: cb337890-fda4-4de7-ae5c-6af8ade82281
Date: Mon, 09 Jul 2018 02:11:01 GMT
Content-Type: application/json;charset=UTF-8
Server: BWS