Bandwidth Scaling of a Shared Bandwidth
Last Updated：2020-10-21
- Capacity expansion of bandwidth of specified shared bandwidth.
Request structure
PUT /v{version}/eipgroup/{id}?{action}&clientToken={clientToken} HTTP/1.1
Host: eip.bj.baidubce.com
Authorization: authorization string
{
"bandwidthInMbps": bandwidthInMbps
}Request header
There are no other special headers except the public headers.
Request parameter
| Parameter name | Type | Required or not | Parameter position | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number (the current value is 1) |
| id | String | Yes | URL parameter | id of shared bandwidth |
| action | String | Yes | Query parameter | For the action executed by shared bandwidth instance, the value in this interface is resize. |
| clientToken | String | Yes | Query parameter | Idempotence Token, for details, please see clientToken |
| bandwidthInMbps | int | Yes | RequestBody parameter | Public network bandwidth, in Mbps. For the EIP Group of prepay type, it is limited to an integer between 10 and 200. |
Return status code
200 is returned successfully, for the failed return, please see Error Code.
Return header
There are no other special headers except the public headers.
Return parameter
No special return parameters
Request example
PUT /v1/eipgroup/eg-b2511000?resize&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
{
"bandwidthInMbps": 10
}Response example
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