Direct Connect Virtual Interfaces
You'll learn: How to configure private and public virtual interfaces on Direct Connect to route traffic between your on-premises network and AWS resources.
What Are Virtual Interfaces?
Once you have a Direct Connect physical connection established (from lesson 2201), you don't just send all traffic down one pipe indiscriminately. Instead, you create virtual interfaces (VIFs) to logically separate and route traffic based on destination type. Think of the physical connection as a highway, and virtual interfaces as dedicated lanes—one for private AWS resources, another for public AWS services.
Private Virtual Interface
A private VIF connects your on-premises network directly to resources inside your VPCs (like EC2 instances, RDS databases, private load balancers). This traffic never touches the public internet—it stays entirely on AWS's backbone.
Configuration steps:
- Specify a VLAN tag (802.1Q)
- Assign BGP ASN for routing
- Attach to a Virtual Private Gateway or Direct Connect Gateway
- Define IP prefixes to advertise
Public Virtual Interface
A public VIF provides access to AWS public services (S3, DynamoDB, CloudFront) over your dedicated connection instead of the internet. You use public IP addresses and BGP to advertise which AWS public prefixes you want to reach.
Use case: Accessing S3 buckets with lower latency and consistent bandwidth compared to internet routing.
Choosing the Right Pattern
- Use private VIF when connecting to VPC resources privately
- Use public VIF when accessing AWS public endpoints with predictable performance
- You can configure multiple VIFs on one Direct Connect to support both patterns simultaneously
Key Takeaway: Virtual interfaces segment Direct Connect traffic logically—private VIFs for VPC resources, public VIFs for AWS public services—allowing flexible, secure connectivity patterns over a single physical connection.