NAT Gateway Resize
Updated at：2025-10-16
Description
Modify the NAT gateway's configuration, applicable only to enhanced NAT gateway instances.
Request structure
Plain Text
1PUT /v{version}/nat/{natId}?{action}&clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "cuNum":3
6}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 | API version number, current value is 1. |
| clientToken | String | Yes | Query | Idempotence token, which is an ASCII string with a length not exceeding 64 bits, see details in [ClientToken Idempotence Support](VPC/API Reference/General Description.md) |
| action | String | Yes | Query | Action executed on the NAT gateway. In this API, the value of this parameter is resize. |
| natId | String | Yes | URL parameter | NAT instance ID |
| cuNum | Integer | Yes | RequestBody | The count of CUs for NAT gateway resizing, ranging from 1 to 100 |
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/nat/nat-b58rnkn1g98h?resize&clientToken=dc31ef8c-5e41-4e38-9ds0-9de75d0ds5b20 HTTP/1.1
2Host: bcc.bj.baidubce.com
3ContentType: application/json
4Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2018-07-05T04:17:29Z/3600/ host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
5
6{
7 "cuNum":20
8} Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Fri, 06 July 2018 07:06:06 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS