Owen has completed the signup process as shown here. During the signup process, Owen selects technop.openvpn.cloud as the web domain for the user portal. This domain uniquely identifies the VPN that will be set up by Owen and is used by Connect Client applications (VPN Client software) to identify the VPN that it needs to connect to.
Owen wants to provide remote access to a private website and other private services hosted in an Amazon Web Services (AWS) Virtual Private Cloud (VPC) to himself and employees.
Illustration of VPN
Owen followed the steps shown below to make the AWS VPC with IP address range of 192.168.0.0/28 part of the VPN.
- Configured a Network to represent the AWS VPC and enters 192.168.0.0/28 as the Subnets for the Network. See, How to add a Network
- Clicked on the download icon next to the Connector created for the Network to reveal various options and selected Launch Connector on AWS from the options list. This started the process of using the CloudFormation template to instantiate a Connector VM in the AWS VPC. See, Launch Connector on AWS
- This newly launched Connector instance is shown with the IP address of 192.168.0.13 in the VPN illustration above. Owen had allowed CloudFormation to create IAM resources, the Connector will automatically configure the VPC route table and update it as needed when Connectors are deployed in other networks.
- As shown in Launch Connector on AWS, Owen added the Security Group of the Connector instance to the inbound rules of the Security Group associated with the webserver at 192.168.0.14. This will allow traffic to be routed through the Connector instance.
- Now Owen connects to OpenVPN Cloud (see, Connecting to OpenVPN Cloud). On connection, Owen can access the application server on the AWS VPC at 192.168.0.14.