Cloud Hosting Platforms and VPS Provisioning

What Is a VPS and Why Does It Matter?

A virtual private server (VPS) is a slice of a physical server that runs its own operating system and behaves like a dedicated machine. Cloud providers such as DigitalOcean, Linode/Akamai, and AWS Lightsail carve large bare-metal servers into many isolated VPS instances using a technology called virtualization. Each instance gets its own CPU allocation, RAM, disk, and public IP address.

For web developers, a VPS is often the first "real" server they manage. Unlike shared hosting, you have root access, which means you can install any software, configure the firewall, and deploy applications exactly as needed. With that power comes responsibility: a misconfigured VPS can expose user data or become a platform for attacks against others.

Choosing a Cloud Provider and Image

All major providers offer a web console where you create and manage instances. Common choices for learners include:

• DigitalOcean — calls VPS instances Droplets
• Linode/Akamai — calls them Linodes
• AWS Lightsail — Amazon's simplified VPS product

When creating an instance, you choose an operating system image. This lab uses Ubuntu LTS (Long-Term Support), which receives security updates for several years and is widely documented. Always prefer the latest LTS release so your system stays supported.

You also select a region (the data center closest to your users or lowest in latency to you), a plan tier (the combination of CPU, RAM, and disk), and a monthly cost. Entry-level plans on most providers start under $10/month. Record all of these details in your lab log — future troubleshooting often depends on knowing exactly what was provisioned.

SSH Key Authentication

Secure Shell (SSH) is the standard protocol for remote terminal access to Linux servers. By default, a new VPS may allow password login, but password authentication is a security risk because automated bots constantly scan the internet for SSH ports and attempt brute-force logins.

Key-based authentication replaces the password with a mathematically linked pair of files:

• Private key — stays on your laptop, never shared with anyone.
• Public key — uploaded to the server. The server uses it to verify that whoever is connecting holds the matching private key.

This lab uses the Ed25519 algorithm, which is modern, compact, and considered strong by current standards. Older RSA keys still work, but Ed25519 is the current best practice.

Generating the Key Pair

On your local machine, open a terminal and run:

```

ssh-keygen -t ed25519 -C "your_email@example.com"

```

Accept the default file location (`~/.ssh/id_ed25519`) or choose a custom path. You will be prompted to enter a passphrase. Use a passphrase — it encrypts the private key on disk so that if your laptop is stolen, the key cannot be used without the passphrase.

The command produces two files:

• `~/.ssh/id_ed25519` — private key (protect this file; permissions should be 600)
• `~/.ssh/id_ed25519.pub` — public key (safe to share)

Uploading the Public Key

Most cloud consoles let you paste the contents of `id_ed25519.pub` into a field during instance creation. Copy it with:

```

cat ~/.ssh/id_ed25519.pub

```

Then paste the output into the provider's SSH key field. The provider injects it into `/root/.ssh/authorized_keys` on the new instance automatically.

Connecting to Your VPS

Once the instance is running (usually within 60 seconds), connect from your terminal:

```

ssh root@<your-server-ip>

```

If your key is in the default location, OpenSSH finds it automatically. If you used a custom path:

```

ssh -i ~/.ssh/id_ed25519 root@<your-server-ip>

```

On first connection, SSH displays a host fingerprint and asks you to confirm. Verify the fingerprint matches what the cloud console shows (some providers display it on the instance detail page) before typing `yes`. This protects against a man-in-the-middle attack where someone intercepts your connection.

Security Basics for a New VPS

Once you have root access, a few immediate steps protect the server:

1. Update packages — run `apt update && apt upgrade -y` to apply security patches.

2. Disable password authentication — edit `/etc/ssh/sshd_config` and set `PasswordAuthentication no`, then restart SSH. This closes the door to brute-force attacks.

3. Firewall — Ubuntu's `ufw` (Uncomplicated Firewall) lets you allow only the ports you need (`ufw allow OpenSSH`, then `ufw enable`).

4. Do not store sensitive credentials on the server in plain text — use environment variables or a secrets manager.

Lab Log Entry

Accurate documentation is a professional habit. Your lab log entry must include: the provider name, instance name, region, Ubuntu LTS version, plan tier (CPU/RAM/disk), the server's public IP address, and the monthly cost estimate from the pricing page. Use the program's standard log template. Incomplete logs are a common reason students do not pass the lab check.

Why This Skill Connects to Your Credentials

CompTIA Linux+ covers managing Linux systems, remote access, and basic security hardening — all practiced here. CompTIA ITF+ introduces foundational computing concepts including networking and cloud basics. Hands-on VPS work builds the operational context that makes those exam topics concrete.