Let’s say we want to create a private network to host our private server which we want to get access from our local computer. The first issue we have to face is to establish a secure connection. We would like to establish a connection to our server using internet, but we want also to avoid any hazardous situation with other people “on the road”. So, this leads to think about getting a VPN connection.
The first step would be to setup our AWS account and start creating our AWS appliances.
We have to go to AWS webpage and sign up, a window like this will pup up:
Fulfill the form and submit it, now you are ready to go!
A VPC appliance is a virtual cloud that allows to isolate instances from the global AWS Cloud. This VPC environment gives us a space where instances and other appliances such as subnets, NAT gateways and Amazon Machines instances (AMI) can be deployed. It is possible to use default VPC’s but also custom ones. A suggested way to create a custom VPC would be:
Go to your AWS console, and login.
On the console panel, select VPC (double clicking). You will get into the VPC Dashboard, or in All services tab look up for Networking and content delivery > VPC
In step 1, select: VPC with Public and Private Subnets, click Select; and you will get in “Step 2: VPC with Public and Private Subnets” as is shown:
Assign a name to your VPC in VPC Name, and choose your Availability Zone for both, private and public subnets. Finally, assign names to your public and private subnets, you can leave it like that if you would rather default names. Please write down your VPC, Public subnet and Private subnet names.
Optional, we could create a NAT gateway to update instances located in private subnets.
Finally, click on Create VPC bottom.
This could be created directed from the Launch instance panel.
