Prerequisites
Before proceeding with the AWS configuration, you must meet the following requirements.
Required Items
- VPN-compatible router - Your router must support VPN connections (IPSec)
- Static IP address - You must obtain a static IP address from your Internet Service Provider. Dynamic DNS will not work for this configuration.
Configuration Overview
This documentation describes the process for establishing a VPC (Virtual Private Cloud) infrastructure using the AWS model referenced as Scenario 3: VPC with Public and Private Subnets and Hardware VPN Access.
This scenario enables you to:
- Deploy both public-facing and private servers within a single cloud environment
- Run web-facing services (like ProPay WEB in IIS) on public servers
- Maintain backend systems in isolated private subnets
- Allow inter-server communication while restricting public access to private resources
Network Architecture
The configuration creates:
| Component | Purpose |
|---|---|
| Public Subnet | Hosts servers accessible from the internet |
| Private Subnet | Hosts internal servers isolated from public access |
| Internet Gateway | Provides internet connectivity to the public subnet |
| VPN Gateway | Connects your local network to the AWS VPC |