What problem does it solve?
Setting up an encrypted IPsec VPN between an on-premises network and AWS involves many interdependent decisions—target gateway, routing type, tunnel bandwidth, device configuration, and monitoring—and mistakes like weak tunnel options, missing route propagation, or single-tunnel setups cause outages that are hard to diagnose.
Core Features & Use Cases
- Connection Creation: Build a Site-to-Site VPN connection in the correct order (customer gateway, target gateway, route propagation, security group, connection) against a virtual private gateway, transit gateway, or Cloud WAN.
- Routing and Bandwidth Decisions: Choose between static and dynamic (BGP) routing, and size tunnels at Standard (1.25 Gbps) or Large (5 Gbps), including VPN Concentrator consolidation for 25+ low-bandwidth sites.
- Resilience and Monitoring: Configure both tunnels for high availability, add a second device for failover, and set up CloudWatch TunnelState alarms and VPN logs to diagnose down tunnels.
- Use Case: A company needs to connect its data center to a VPC over an encrypted tunnel with BGP failover; the skill walks through gateway selection, connection creation with strong AES-256/SHA-256 tunnel options, device configuration guidance, and CloudWatch alarming.
Quick Start
Ask the agent to create a Site-to-Site VPN connection from your on-premises network to your VPC, specifying the target gateway type, routing preference, and customer gateway public IP.