Direct Connect Virtual Interfaces
You'll learn: How to create and manage the three types of virtual interfaces (VIFs) that enable different traffic patterns over AWS Direct Connect connections.
What Are Virtual Interfaces?
Think of your Direct Connect physical connection as a multi-lane highway between your data center and AWS. Virtual Interfaces (VIFs) are the dedicated lanes on that highway, each serving different types of traffic. Without a VIF, your physical connection exists but carries no data—like building a highway without painting lanes or setting traffic rules.
The Three VIF Types
Private Virtual Interface
Routes traffic to resources inside your VPCs using private IP addresses. This is your lane for reaching EC2 instances, RDS databases, and other VPC-hosted services without touching the public internet.
- Connects to a Virtual Private Gateway or Direct Connect Gateway
- Uses BGP to exchange private IP routes
- One private VIF per VPC (or use Direct Connect Gateway for multi-VPC)
Public Virtual Interface
Provides access to AWS public services (S3, DynamoDB, public endpoints) using public IP addresses you own. Traffic stays on the AWS backbone, bypassing the internet.
- Requires AWS to advertise all public AWS IP prefixes
- You must own public IP space and advertise it via BGP
- Only one public VIF needed per Direct Connect connection
Transit Virtual Interface
Connects to an AWS Transit Gateway, enabling scalable routing to multiple VPCs and on-premises locations through a central hub.
- Best for complex, multi-VPC architectures
- Simplifies route management at scale
- Requires Transit Gateway setup first
Configuration Essentials
Each VIF requires: a VLAN ID, BGP ASN, BGP peer IPs, and authentication key. AWS provides BGP peering details after you create the VIF.
Key Takeaway: Virtual interfaces transform your Direct Connect physical link into purpose-built data paths—private VIFs for VPC access, public VIFs for AWS services, and transit VIFs for hub-based routing architectures.