Create a NAT gateway
Creates a managed NAT gateway that gives VMs in a VPC outbound internet access without public IPs of their own. Requires scope: network.write.
Authentication
IBEE platform API token. Production tokens start with ibee_prod_key_; development tokens start with ibee_dev_key_. Use a token only with its matching gateway environment.
Path parameters
Headers
Retry key for this create. Send the same key and the same body on every retry. The key is scoped to organization, workspace and path.
- Create completed: you get the original answer for 24 hours, even if the plan limit has since been reached.
- Refused or never sent: nothing was created, so the key is free to use again, including with a corrected body.
- Unknown outcome (timeout, server error, lost connection): 409
idempotency_in_progresswithRetry-After. This usually lasts 30 seconds and at most 3 minutes. Keep retrying with the same key and body. The next retry returns the Reserved IP, subnet or NAT gateway. For a VPC, firewall group or port forward, it either creates the resource or answers 409 “already exists”. - Changed body, while the outcome is unresolved or after the create completed: 409
idempotency_conflict. - New key at the plan limit: 402.
Query parameters
The positive numeric workspace ID to scope this request to. Zero, negative, and non-numeric values are rejected.
Request
Subnet the gateway is placed in; chosen by the service when omitted.
Reserved IP to use as the gateway’s public address; a platform-assigned address is used when omitted.
Display name of the gateway. Default NAT Gateway.
Response
Lifecycle status of a VPC, subnet, NAT gateway or port-forwarding rule.
provisioning: being created.available: ready for use.error: the last change failed; seeerror_message.deleting: being removed.
Error detail when status is error.
