Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
NAT Gateway → Update Rule
AI-generatedSummary
Update a NAT Gateway rule in the specified datacenter. Supply the gateway and rule IDs, then set any rule properties to include in the update; protocol is described as immutable and is only used during creation.
Inputs
- Datacenter ID (required) — ID of the datacenter containing the NAT Gateway.
- NAT Gateway ID (required) — ID of the NAT Gateway.
- Rule ID (required) — ID of the NAT Gateway rule to update.
- Rule Properties — Optional update fields: name, public IP, source subnet, target port range, target subnet, type (SNAT), and protocol. Protocol is marked immutable and only used during creation. The port range has start and end values.
- Include Request Status — Defaults to false. When enabled, includes request tracking ID and status URL from the asynchronous operation, if returned.
- Include Response Headers — Defaults to false. When enabled, returns the response body under a body key alongside headers and status code.
- Request Options — Optional batching, SSL certificate validation, proxy, and timeout settings.
Output shape
A single API response item, optionally wrapped with response metadata.
The operation-scoped source pack contains no implementation bodies, so the exact response body fields and whether an update returns a body are not visible. With Include Response Headers enabled, the body is nested under body and accompanied by headers and statusCode; Include Request Status can add tracking ID and status URL.
Examples
Example 1: Change a rule's name and source subnet
Set the datacenter, NAT Gateway, and rule IDs, then provide the new name and source subnet in Rule Properties.