Overview
Routes that send specific destination ranges through a private gateway instead of the VPC’s default path — “Configure custom routing rules for your VPC”.Navigation: Networking → VPC → click a VPC → Static Routes.
What a row shows
The Gateway column shows the gateway’s raw identifier, not its IP address. Matching a route to a gateway means comparing IDs against Private Gateway — the readable address isn’t shown here.With more than one private gateway, note the ID-to-address mapping somewhere before you start adding routes.
Adding a route
Add Route takes a CIDR and a Private Gateway. With no private gateway you get:The validation gap
Common task: route an on-premises range through a private gateway
1
Confirm the private gateway exists and is up
Private Gateway. Note its identifier as well as its IP — the identifier is what this screen shows.
2
Get the exact destination ranges
From whoever runs the far network. One route per range; don’t approximate with a wider range that overlaps something.
3
4
Add the route and re-read the CIDR
Since nothing validates it, this read-back is the validation.
5
Test from a machine, over the console
Use the console. A routing change that goes wrong can drop your SSH session, and then you’re locked out of the machine you were testing from.
Before deleting a private gateway
Related
Private Gateway
The gateway routes point through.
Details
The VPC’s own CIDR, to check for overlap.
Networks
The tier CIDRs, for the same reason.
Network Designer
Routes appear as a route table node.