Create a NAT gateway
Creates a NAT gateway in a subnet of a VPC and allocates its public IPv4 address, which is in the answer at once. The gateway is provisioning until it can carry traffic, then active; poll it at Location. Nothing is routed to it until a route table names it as a natGateway target. Refused with 409 network_gateway_required when the VPC has no attached network gateway, 409 subnet_not_public when the subnet's route table has no 0.0.0.0/0 route to that network gateway, 409 host_unsupported where NAT gateways aren't available, and 409 quota_exceeded at network.natGatewaysPerProject. The address doesn't count against network.ipv4AddressesPerOrganization.
https://network-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/nat-gatewaysAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
202
Accepted: the NAT gateway, provisioning (also at Location; poll it after Retry-After, 2 seconds).
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.