Route Tables in Thalassa Cloud VPCs
A route table defines how network traffic is directed within a Virtual Private Cloud (VPC) in Thalassa Cloud. Route tables contain rules that specify the destination and next hop for packets traveling between subnets, other VPCs, and external networks.
Route Table Capabilities
| Capability | Description |
|---|---|
| Custom Routing Rules | Users can define routes to control how traffic flows within the VPC and external networks. |
| Subnet Association | Each subnet can be associated with only one route table, ensuring clear and consistent traffic control. |
| Multiple Route Targets | Routes can point to various targets, such as NAT gateways, VPC gateways, and load balancers. |
| Default Route Table | Every VPC has a default route table, but users can create and assign custom route tables as needed. |
Route Table Behavior and Constraints
Custom Routing Rules
Route tables in Thalassa Cloud allow users to define routing rules for directing traffic within a VPC. Each route consists of a destination CIDR block and a next-hop target, such as a gateway or NAT service.
Subnet Association
Each subnet must be associated with one route table at a time. When a subnet is created, it automatically associates with the default route table of the VPC unless a custom route table is explicitly assigned.
Default Route Table
Every VPC has a default route table that provides basic connectivity. Users can create additional route tables for more granular traffic control. If a subnet does not have a custom route table assigned, it falls back to the default route table.
Routing Targets
Routes in Thalassa Cloud support various targets, including:
- VPC Gateways – Allow connectivity to other VPCs within the same environment.
- NAT Gateways – Enable outbound internet access for private subnets.
- Load Balancers – Facilitate traffic distribution for applications.
Traffic Flow and Constraints
Route tables dictate how packets travel within and outside a VPC. Once a route table is assigned to a subnet, all traffic from that subnet follows the defined rules. Overlapping routes are not supported, and the most specific route match is always used.
Summary
Route tables in Thalassa Cloud are critical for managing network traffic flow within a VPC. They define how traffic moves between subnets, VPCs, and external destinations while ensuring isolation and security. Each VPC has a default route table, but users can create additional route tables to enforce more specific routing policies.
By assigning route tables to subnets, users ensure proper traffic segmentation, connectivity optimization, and security enforcement within their cloud environment.