Skip to main content

Deploying Infrastructures Using Terraform on UpCloud

Terraform is a tool to help us deploy infrastructures on any cloud provider such as AWS, GCP, DigitalOcean, and many more. Unlike Amazon CloudFormation which is specific only for AWS, Terraform supports many cloud providers found in Terraform's registry. It uses a domain-specific language built clearly for provisioning and configuring infrastructures named HCL or HashiCorp Configuration Language.

Meanwhile, UpCloud is an alternative cloud provider for SMEs. It targets a quite similar segment to DigialOcean and Linode. It provides a variety of popular solutions in the cloud such as managed Redis database, S3-compatible storage, private network, load balancer, and so on. Even though its cost is a little bit higher than DigitaOcean or others, it provides quite complete features on each service like the features of the load balancer that we will use in this post. Moreover, it actively publishes new features like the managed OpenSearch database published recently.

For instance, we will build an infrastructure to host a simple web server with an architecture like the following image. The server will be accessed by a domain name with an HTTPS connection.

Simple web server deployment on UpCloud

Several services that will be deployed include.

  • Private network and the router
  • Server to host the web service
  • Load balancer, including its backend and frontend rules
  • Dynamic certificate for HTTPS

First, we define some variables required for some resources. We store it in variable.tf.

# basic variables

variable "upcloud_username" {
  description = "UpCloud username"
  type = string
}

variable "upcloud_password" {
  description = "UpCloud password"
  type = string
}

variable "upcloud_zone" {
  description = "UpCloud zone"
  type = string
  default = "sg-sin1"
}

# networking

variable "my_router_name" {
  description = "Basic network router name"
  type = string
  default = "basic-net-router"
}

variable "my_network_name" {
  description = "Basic private network name"
  type = string
  default = "basic-net"
}

variable "my_lb_name" {
  description = "Basic load balancer name"
  type = string
  default = "basic-lb"
}

# server

variable "server_hostname" {
  description = "Server hostname"
  type = string
  default = "terraform.lukinotes.com" # change to your domain
}

variable "server_port" {
  description = "Default web server port"
  type = number
  default = 8080
}

variable "server_private_ip" {
  description = "Manual private IP address for the server"
  type = string
  default = "10.0.0.10" # it means we will need a private network with subnet 10.0.0.0/24
}

Second, we create a configuration file, config.tf, to set up our provider which is UpCloud.

terraform {
  required_providers {
    upcloud = {
      source  = "UpCloudLtd/upcloud"
      version = "~> 2.0"
    }
  }
}

Third, we define networking and server resources in main.tf file. We also need to prepare the public certificates of our devices because we will use public key authentication for remote accessing our server through SSH connection. Our server will be attached to a public network, private network, and utility network of our account. We enable daily backup for our server because it is free on UpCloud.

provider "upcloud" {
  username = var.upcloud_username
  password = var.upcloud_password
}

# private network

resource "upcloud_router" "sample" {
  name = var.my_router_name
}

resource "upcloud_network" "sample" {
  name = var.my_network_name # required
  zone = var.upcloud_zone # required
  router = upcloud_router.sample.id

  ip_network { # required
    address            = "10.0.0.0/24" # required
    dhcp               = true # required
    dhcp_default_route = false # is the gateway the DHCP default route?
    family             = "IPv4" # required
    gateway            = "10.0.0.1"
  }
}

# basic server

resource "upcloud_server" "sample" {
  hostname = var.server_hostname
  zone     = var.upcloud_zone
  plan     = "1xCPU-2GB"

  template {
    storage = "Ubuntu Server 22.04 LTS (Jammy Jellyfish)"
    size    = 50
    filesystem_autoresize = true
    delete_autoresize_backup = true
  }

  simple_backup {
    plan = "daily"
    time = "1900"
  }

  network_interface {
    type = "public"
  }

  network_interface {
    type = "private"
    network = upcloud_network.sample.id
    ip_address_family = "IPv4"
    ip_address = var.server_private_ip
    source_ip_filtering = true
  }

  network_interface {
    type = "utility"
  }

  login {
    user = "root"
    create_password = false

    keys = [
      "ssh-rsa abcabc pc1",
      "ssh-rsa xyzxyz pc2"
    ]
  }

  metadata = true

  labels = {
    env    = "dev"
    owner  = "luki"
  }

  # sample provisioning
  user_data = <<-EOF 
     #!/bin/bash
     echo "Hello, World!" > index.html
     nohup busybox httpd -f -p ${var.server_port} &
     EOF
}

Next, we define the load balancer and its components including frontend, backend, and certificates. We store it in loadbalancer.tf file.

resource "upcloud_loadbalancer" "sample" {
  configured_status = "started"
  name              = var.my_lb_name    # required
  plan              = "development"     # required
  zone              = var.upcloud_zone  # required

  # 0
  networks {
    name    = var.my_network_name # required
    type    = "private"   # required
    family  = "IPv4"      # required
    network = upcloud_network.sample.id
  }

  # 1
  networks {
    name   = "public-net"
    type   = "public"
    family = "IPv4"
  }
}

# BE

resource "upcloud_loadbalancer_backend" "sample" {
  loadbalancer = upcloud_loadbalancer.sample.id
  name         = "lb-be-sample"
}

## Attach our server as BE handler

resource "upcloud_loadbalancer_static_backend_member" "sample_1" {
  backend      = upcloud_loadbalancer_backend.sample.id
  name         = "lb-be-sample-1"
  ip           = upcloud_server.sample.network_interface[1].ip_address # private ip address
  port         = var.server_port
  weight       = 100
  max_sessions = 1000
  enabled      = true
}

# FE http

resource "upcloud_loadbalancer_frontend" "sample" {
  loadbalancer         = upcloud_loadbalancer.sample.id
  name                 = "lb-fe-sample"
  mode                 = "http"
  port                 = 80
  default_backend_name = upcloud_loadbalancer_backend.sample.name

  networks {
    name = upcloud_loadbalancer.sample.networks[1].name # public network
  }
}

## Redirect HTTP to HTTPS for default server

resource "upcloud_loadbalancer_frontend_rule" "sample_redirect_secure" {
  # required

  frontend = upcloud_loadbalancer_frontend.sample.id
  name = "redirect-https"
  priority = 60

  # optional

  actions {
    http_redirect {
      scheme = "https"
    }

    set_forwarded_headers {
      active = true
    }
  }

  matchers {
    header {
      name = "Host"
      method = "starts"
      value = var.server_hostname
      ignore_case = true
    }
  }
}

# FE https

resource "upcloud_loadbalancer_frontend" "sample_secure" {
  loadbalancer         = upcloud_loadbalancer.sample.id
  name                 = "lb-fe-sample-secure"
  mode                 = "http"
  port                 = 443
  default_backend_name = upcloud_loadbalancer_backend.sample.name

  networks {
    name = upcloud_loadbalancer.sample.networks[1].name # public network
  }
}

## Handle HTTPS request for default server

resource "upcloud_loadbalancer_frontend_rule" "sample_secure_serve" {
  # required

  frontend = upcloud_loadbalancer_frontend.sample_secure.id
  name = "serve-http-default"
  priority = 50

  # optional

  actions {
    use_backend {
      backend_name = upcloud_loadbalancer_backend.sample.name
    }

    set_forwarded_headers {
      active = true
    }
  }

  matchers {
    header {
      name = "Host"
      method = "starts"
      value = var.server_hostname
      ignore_case = true
    }
  }
}

# dynamic certs
resource "upcloud_loadbalancer_dynamic_certificate_bundle" "sample_dyn" {
  name = "sample-dyn"
  hostnames = [
    var.server_hostname
  ]
  key_type = "rsa"
}

# attach certificate
resource "upcloud_loadbalancer_frontend_tls_config" "sample_secure" {
  name               = "sample"
  frontend           = upcloud_loadbalancer_frontend.sample_secure.id
  certificate_bundle = upcloud_loadbalancer_dynamic_certificate_bundle.sample_dyn.id
} 

Finally, we output some values that are necessary like the IP address and DNS name of the deployed load balancer. We need to add the load balancer address into the DNS record of our domain as a CNAME record.

output "public_ip_address" {
  description = "Server IPv4 address"
  value = upcloud_server.sample.network_interface[0].ip_address
}

output "loadbalancer_networks" {
  description = "Public address of the load balancer"
  value = [ for item in upcloud_loadbalancer.sample.networks : { dns_name = item.dns_name, type = item.type, name = item.name } ]
}

Then, we can run the following commands.

terraform init
terraform plan
terraform apply

Comments

Popular posts from this blog

Rangkaian Sensor Infrared dengan Photo Dioda

Keunggulan photodioda dibandingkan LDR adalah photodioda lebih tidak rentan terhadap noise karena hanya menerima sinar infrared, sedangkan LDR menerima seluruh cahaya yang ada termasuk infrared. Rangkaian yang akan kita gunakan adalah seperti gambar di bawah ini. Pada saat intensitas Infrared yang diterima Photodiode besar maka tahanan Photodiode menjadi kecil, sedangkan jika intensitas Infrared yang diterima Photodiode kecil maka tahanan yang dimiliki photodiode besar. Jika  tahanan photodiode kecil  maka tegangan  V- akan kecil . Misal tahanan photodiode mengecil menjadi 10kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 10 / (10+10) x Vcc V- = (1/2) x 5 Volt V- = 2.5 Volt Sedangkan jika  tahanan photodiode besar  maka tegangan  V- akan besar  (mendekati nilai Vcc). Misal tahanan photodiode menjadi 150kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 150 / (150+10) x Vcc V- = (150/160) x 5

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the exi

Resize VirtualBox LVM Storage

VirtualBox is a free solution to host virtual machines on your computer. It provides configuration options for many components on our machine such as memory, storage, networking, etc. It also allows us to resize our machine storage after its operating system is installed. LVM is a volume manager in a Linux platform that helps us to allocate partitions in the system and configure the storage size that will be utilized for a specific volume group. There are some points to be noticed when we work with LVM on VirtualBox to resize our storage. These are some steps that need to be performed. 1. Stop your machine before resizing the storage. 2. Set new storage size using GUI by selecting " File > Virtual Media Manager > Properties " then find the desired virtual hard disk name that will be resized. OR , by running a CLI program located in " Program Files\Oracle\VirtualBox\VBoxManage.exe ".  cd "/c/Program Files/Oracle/VirtualBox" ./VBoxManage.exe list

Installing VSCode Server Manually on Ubuntu

I've ever gotten stuck on updating the VSCode server on my remote server because of an unstable connection between my remote server and visualstudio.com that host the updated server source codes. The download and update process failed over and over so I couldn't remotely access my remote files through VSCode. The solution is by downloading the server source codes through a host with a stable connection which in my case I downloaded from a cloud VPS server. Then I transfer the downloaded source codes as a compressed file to my remote server through SCP. Once the file had been on my remote sever, I extracted them and align the configuration. The more detailed steps are as follows. First, we should get the commit ID of our current VSCode application by clicking on the About option on the Help menu. The commit ID is a hexadecimal number like  92da9481c0904c6adfe372c12da3b7748d74bdcb . Then we can download the compressed server source codes as a single file from the host.

Beautiful Rain (JDorama)

Saya selalu tertarik dengan film-film inspirasional, baik movie atau pun serial drama. Akhir-akhir ini saya tertarik untuk menonton drama serial jepang. Saya googling dengan keyword "inspirational japan dorama" kemudian saya dapati sejumlah review  beberapa film bagus dari sejumlah netizen.  Salah satu yang kemudian saya tonton adalah Beautiful Rain . Setiap episode film ini selalu membuat saya sangat terharu sampai meneteskan air mata. :' Yah, ini mungkin saja karena saya yang terlalu melankolis. Hahaha. Ini sedikit review dari saya tentang film ini.

How To Use Protocol Buffer in Javascript

We have understood a few advantages of protocol buffer like what I've explained in my other post . Now, let's look at how we can implement it in our code. The "transpiler" tool, named protoc , supports the generation of a helper class for managing the object instance in a variety of programming languages. In this post, we use Javascript as an example and run in a Linux environment. Preparation Before we develop our code, we should install protoc for generating the helper class. Download protoc binary from the release page . Extract the content and store the directories  ( bin  and  includes ) in /usr/local  directory so that the executable binary can be accessed directly. Run protoc --help to check its manual. Install a required dependency globally to enable protoc  to generate the Javascript files by running: npm i -g protoc-gen-js . Create a proto file First, we should create an empty directory