How xxradar/aws_route_server_demo works
Project Type and Purpose
• Project Type: AWS infrastructure configuration tutorial
• Purpose: Walk through enabling dynamic BGP-based routing in a single VPC using AWS VPC Route Server and peering to external network devices (e.g., FortiGate).
Main Components
a. IAM Layer
– RouteServerPolicy (JSON)
– TrustPolicy (JSON)
– IAM Role (RouteServerRole) that assumes trust policy and attaches the RouteServerPolicy
b. VPC & Subnets
– VPC (e.g., vpc-571faf2e)
– One or more subnets (e.g., subnet-7a0ae703)
c. AWS VPC Route Server
– The managed Route Server instance (rs-xxxxx)
– Associated ENI endpoints (rse-xxxxx) placed in subnets
d. Route Tables
– One or more route tables (rtb-xxxxx) with propagation enabled
e. External Network Devices (BGP Peers)
– Example device with IP 10.0.2.3 initiating BGP session
– BGP options (PeerAsn=65001, liveness detection=bfd)
f. Dynamic Routing Flow
– BGP sessions between Route Server ENI and external device
– Route-Server propagates learned routes into AWS route tables
Relationships & Interactions
• IAM Role → AWS EC2 Create/Manage Route Server
• VPC ↔ Associate Route Server
• Subnet → Route Server Endpoint (ENI)
• Route Server ↔ Route Tables (propagation in/out)
• ENI ↔ External Device (BGP peer over TCP 179)
Architectural Patterns & Principles
– Centralized dynamic routing: the Route Server acts as a hub for all subnet route exchanges.
– Separation of concerns: IAM policies/roles distinct from networking resources.
– AWS-managed service reduces customer-side complexity.