Atomically replace the static-route set on a route table.
curl --request PUT \ --url https://stratum.example.com/v1/projects/example/network/route-tables/example/routes \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "items": [ { "destinationCidr": "example", "targetType": "internetGateway", "targetId": "example", "state": "active" } ] }'PUT semantics mirroring security-group rules: the provided list is the new route set in its entirety, applied in a single transaction. Cap: 50 routes per table.
Local (intra-VPC) routing is implicit and cannot be
overridden: a destinationCidr lying inside the VPC CIDR or
link-local space (169.254.0.0/16) is rejected, while broad
routes containing them (e.g. 0.0.0.0/0) are allowed and
never capture local traffic. Duplicate destinations are
rejected.
Supported targets: networkInterface / instance (next hop
= the NIC’s private IP; classic NAT-instance / firewall /
VPN-appliance routing), internetGateway (explicit egress
via the VPC’s provider gateway; requires the VPC to have
internetGateway: true), and vpcPeering (an ACTIVE
peering connection this VPC is a member of; next hop = the
peer side of the connection’s link — add a route in BOTH
VPCs for two-way traffic), and natGateway (an available
NAT gateway in this VPC; requires internetGateway: true).
A natGateway route sends the traffic out the provider
gateway and makes every subnet associated with the table
egress with the gateway’s floating IP as its source — one
gateway can serve many subnets, and different tables can
point at different gateways.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”object
object
IPv4 CIDR this route matches on the destination address. Must not lie inside the VPC CIDR (intra-VPC routing is implicit) or link-local space; broad routes containing them (e.g. 0.0.0.0/0) are fine — local traffic always wins, as with AWS’s non-overridable local route.
Target resource ID. Required for every target type except internetGateway (a VPC has at most one implicit IGW). For instance targets this is the instance ID; the route resolves to its primary NIC.
Server-populated; ignored on input. A route whose target no longer exists is reported as blackhole and not programmed into the fabric.
Responses
Section titled “Responses”Routes replaced.
object
object
IPv4 CIDR this route matches on the destination address. Must not lie inside the VPC CIDR (intra-VPC routing is implicit) or link-local space; broad routes containing them (e.g. 0.0.0.0/0) are fine — local traffic always wins, as with AWS’s non-overridable local route.
Target resource ID. Required for every target type except internetGateway (a VPC has at most one implicit IGW). For instance targets this is the instance ID; the route resolves to its primary NIC.
Server-populated; ignored on input. A route whose target no longer exists is reported as blackhole and not programmed into the fabric.
Example
{ "items": [ { "targetType": "internetGateway", "state": "active" } ]}Bad request.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Resource not found.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}