Terraaform VPN server for GCP (WireGuard Server)

This is a Terraform Infrastructure-as-Code (IaC) project to deploy WireGuard VPN Server on Google Cloud Platform (GCP), and crate VPN clients, for users to tunnel through (my very own private VPN).

Overview
Setup
Deploy
Clean-up
Terraform

Overview

The codes in this folder create and deploy VMs on GCP Compute Engine automatically, with the following configurations:

Server Configuration	Value
CPU	1
VM Type	Spot, e2-micro
RAM	3.75 GB
Storage	10 GB
Storage Type	Sold State Drive (SSD)
Delete Protection	True
Region	europe-west2
IP type	static

Setup

Before getting started, ensure you have done the following prerequisites:

Install Terraform: Version 0.12.x or higher. Follow the installation instructions from Terraform.
Install Google Cloud SDK: Required for authentication and interacting with GCP services. Follow installation instructions from Google Cloud.

You'll also need appropriate permissions and credentials to manage resources within your GCP project, preferably using a IAM Service Account with realavant privileges.

Now the setup:

Set the GCP project values in the provider.tf file, according to the project details from your GCP console.
Get or create the credential file (json key) for an IAM Service Account with the required roles, download, and paste it to this folder, renaming it as cred.json.
Initialize the project, as follows:
```
terraform init
```

Deploy

Make changes according to your requirements (if needed).
Review the infrastructures and configurations that are to be created:
```
terraform plan
```
Deploy the infrastructure to the cloud:
```
terraform apply
```

After vpn server is provisioned, run the following script to create wireguard vpn clients:
Note: Change the PEERS value accordingn to your desired number of VPN clients/users you want to create.

docker run -d \
  --name=wireguard \
  --cap-add=NET_ADMIN \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e PEERS=1 \
  -p 51820:51820/udp \
  -v /var/config:/config \
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" \
  --restart unless-stopped \
  lscr.io/linuxserver/wireguard:latest

Next, run the following command for each PEER and copy-paste the code to WireGuard clent, or save as .conf file:
```
sudo cat /var/config/peer1/peer1.conf
```

Clean-up

If and when the cloud infrastructure needs to be deleted/destroyed, run the following command:

terraform destroy

Terraform

Managing infrastructure manually can be error-prone, time-consuming, and difficult to replicate across environments. Infrastructure as Code (IaC) addresses these challenges by allowing us to define our infrastructure using code, which can then be versioned, tested, and automated. This repository serves as the central location for all the code related to our GCP infrastructure. It includes configurations, templates, and scripts necessary for provisioning and managing resources such as virtual machines, networking components, databases, and more:

Declarative Configuration: Define infrastructure using declarative configuration files, making it easy to understand and maintain.
Version Control: Store infrastructure configurations alongside application code for versioning and collaboration.
Automated Provisioning: Automate the provisioning and configuration of infrastructure, reducing manual errors and saving time.
Scalability: Easily scale infrastructure up or down by modifying configuration files and re-running deployments.
Consistency: Ensure consistency across environments (development, staging, production) by using the same configuration.