Getting started with dynamic route servers (beta)
Dynamic Route Server for VPC is a beta feature that is available for evaluation and testing purposes to select customers. Access is restricted to allowlisted accounts.
Dynamic Route Server for VPC is designed for complex network topologies that require scalable, resilient, and automated routing, reducing the need for manual route configuration.
You can use a dynamic route server to dynamically manage routing between your Virtual Private Cloud (VPC) and connected networks, such as transit gateways, firewalls, SD-WAN devices, and overlay networks. A dynamic route server uses Border Gateway Protocol (BGP) to learn and advertise routes, and applies policy-driven routing logic to automatically update VPC routing tables and peer connections as network conditions change.
Before you begin
Before you provision a dynamic route server:
- Make sure that you have the required level of access to create VPC services. For more information, see Getting started with Virtual Private Cloud and Managing IAM access for VPC Infrastructure Services.
- Review Planning considerations for dynamic route servers to understand BGP, ASN, and routing table requirements.
- Create a VPC and provision one or more virtual network interfaces (VNIs). The dynamic route server uses the VNIs to deploy routing appliances and establish BGP sessions with peers.
Setting up a dynamic route server
To set up a dynamic route server, follow these general steps:
- Create a dynamic route server instance and add at least one member.
- Create a peer group for the dynamic route server instance.
- Attach peers, such as firewalls, routers, or transit gateways, to the peer groups.
- Create peer group policies to control how routes are learned, advertised, or added to VPC routing tables.
- Optionally, create static routes to define fixed network paths that are managed by the dynamic route server. Static routes are health-aware and are automatically added to or removed from VPC routing tables based on the health of the associated next-hop peer group.
Next steps
After your dynamic route server is set up, consider these next steps:
- Explore Dynamic route server use cases for guidance on common topologies such as routing through a firewall, multi-zone deployments, and active and standby failover.
- Read Dynamic route server architecture to understand how the service components, routing appliances, and Transit Gateway integration work together.