Kvindo™ Cloud Docs
A Route Table Attachment binds a Route Table to either a whole VPC or a single VPC Subnet, making that table's routes active for that VPC's (or that subnet's) traffic.
• Route Table — the table of routes to apply (spec.routeTableId)
• VPC — attach VPC-wide: the routes apply to all traffic in the VPC (spec.vpcId)
• VPC Subnet — attach to a single subnet only: the routes apply solely to that subnet's traffic, leaving the rest of the VPC unaffected (spec.vpcSubnetId)
vpcId and vpcSubnetId are mutually exclusive — set exactly one. Create the Route Table (and its routes) and the VPC or VPC Subnet first, then attach them.
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Route Table | spec.routeTableId |
spec.route_table_id |
No | ULID — references a Route Table | — | No | The route table to apply |
| VPC | spec.vpcId |
spec.vpc_id |
No | ULID — references a VPC | — | No | Attach VPC-wide. Mutually exclusive with VPC Subnet |
| VPC Subnet | spec.vpcSubnetId |
spec.vpc_subnet_id |
No | ULID — references a VPC Subnet | — | No | Attach to a single subnet only. Mutually exclusive with VPC |
Attach an existing route table to an existing VPC.
Terraform
Python SDK
kc CLI
Resource docs
More in this section
Reference