VPN Architecture
In this setup, your VPC uses the CIDR block10.0.0.0/16 and contains private subnets without public IPs. To connect on-premises devices:
- AWS deploys a Virtual Private Gateway (VGW), which terminates the IPsec tunnel on the VPC side.
- Your on-premises network uses a Customer Gateway (CGW) appliance with a public IP (e.g.,
1.1.1.1). - AWS assigns a public IP (e.g.,
2.2.2.2) to the VGW. - An IPsec tunnel encrypts traffic between the CGW and VGW over the Internet.

Key Components
Routing Options
You can route traffic between10.0.0.0/16 (VPC) and 192.168.0.0/16 (on-premises) in two ways:
1. Static Routing
Manually add routes to your VPC route table.2. Dynamic Routing (BGP)
Use the Border Gateway Protocol (BGP) to exchange and propagate routes automatically between the Customer Gateway and the VPN Gateway.
Dynamic routing via BGP adds complexity. Ensure your on-premises router supports BGP and proper autonomous system (AS) configuration.
Pricing
AWS Site-to-Site VPN pricing includes two main components:
Data transferred into AWS over the VPN is free; only outbound data is charged.
VPN Gateway Limits
Each AWS-managed VPN tunnel supports:
To increase throughput, you can deploy multiple tunnels and use Equal-Cost Multi-Path (ECMP) routing.

Summary
Connecting your on-premises network to an AWS VPC using VPN delivers secure, encrypted traffic flow:- Virtual Private Gateway (VGW): AWS-side endpoint attached to your VPC.
- Customer Gateway (CGW): On-premises endpoint with a public IP.
- IPsec Tunnel: Secures data in transit over the public Internet.
- Routing: Static routes for simplicity or BGP for automation.
- Pricing: Charged by VPN connection hours and outbound data.
- Limits: 1.25 Gbps per tunnel, 140,000 pps, 1466 byte MTU.

