How to Get Started with a Cloud Server: A Practical Beginner Guide

About 12 min

How to Get Started with a Cloud Server: A Practical Beginner Guide

Trying a cloud server for the first time can feel more difficult than it really is. Provider dashboards contain terms such as vCPU, RAM, NVMe, snapshots, bandwidth, SSH keys, images, firewalls, and regions. After the server is created, you still need to connect to Linux and decide what to install.

The good news is that you do not need to understand every cloud feature before you begin.

For a first project, your goal should be simple:

Rent one small Ubuntu server, secure it, publish one working website, create a backup, and learn how to delete the server when you are finished.

This guide explains that complete workflow. It also compares five reliable cloud server providers:

The commands below use Ubuntu 24.04 LTS, but most also work on Ubuntu 22.04 LTS.

What Is a Cloud Server?

A cloud server is a virtual machine running inside a provider's data center. It has its own operating system, CPU allocation, memory, storage, network connection, and public IP address.

The terms cloud server and VPS are often used interchangeably in beginner hosting discussions. There can be architectural differences between products, but both normally give you:

administrator or root access
a Linux or Windows operating system
a public IP address
the ability to install your own software
independent CPU, memory, disk, and bandwidth limits

A cloud server is useful for:

learning Linux
hosting a website or blog
running a Node.js or Python API
deploying Docker containers
operating a Telegram or Discord bot
creating a VPN or private development environment
hosting a small database
running scheduled automation scripts

It is different from shared hosting. With shared hosting, the provider manages most of the server. With a VPS, you are responsible for updates, security, backups, software, and troubleshooting.

What Should a Beginner Learn First?

You do not need Kubernetes, Terraform, load balancers, or a multi-server architecture for your first experiment.

Learn these seven skills first:

Choose a sensible server size and region.
Connect with SSH.
Create a non-root user.
Install updates and configure a firewall.
Install a web server.
Connect a domain and enable HTTPS.
Back up and monitor the server.

Once you can repeat this process without following every command blindly, you have a solid cloud server foundation.

Recommended First Server Configuration

For learning Linux or hosting a small project, start with:

Resource	Beginner Recommendation
Operating system	Ubuntu 24.04 LTS
CPU	1-2 vCPU
Memory	1-2 GB RAM
Storage	25-50 GB SSD or NVMe
Network transfer	At least 1 TB per month
IP address	One public IPv4 address
Authentication	SSH key
Backup	Snapshot plus an off-server copy

Use 1 GB RAM for command-line learning or a static website. Choose 2 GB RAM if you want to install Docker, WordPress, a database, or a Node.js application.

Do not start with a large instance. A bigger server does not make an insecure or incorrectly configured application reliable. Most providers let you resize later.

How to Choose a Cloud Server Provider

For a first server, compare providers using practical criteria rather than headline price alone.

1. Region

Choose a data center near your users. Geographic distance affects latency, especially for APIs, dashboards, remote desktops, and dynamic websites.

2. Billing

Hourly billing is useful for learning because you can create a server, test it, and delete it without paying for a long contract. Always check whether storage, snapshots, backups, public IPv4 addresses, and bandwidth are billed separately.

3. Dashboard

A beginner-friendly control panel should make these actions easy:

deploy and rebuild a server
reset access credentials
add SSH keys
view bandwidth usage
create snapshots
configure cloud firewall rules
resize or delete the instance

4. Documentation

Good documentation matters more than many beginners expect. You will eventually need instructions for SSH, DNS, backups, recovery, firewalls, and billing.

5. Recovery Options

Check whether the provider supports snapshots, automatic backups, a browser console, rescue mode, or server rebuilds. These features are valuable when an SSH or firewall mistake locks you out.

Quick Comparison: 5 Reliable Cloud Server Providers

Provider	Best For	Main Strength	Beginner Consideration
LightNode	Flexible global testing	Hourly billing and 40+ locations	Good when region choice matters
DigitalOcean	First developer VPS	Clean dashboard and extensive tutorials	Managed add-ons can increase cost
Vultr	Fast global deployment	Broad infrastructure options	Product selection can feel wide
Hetzner Cloud	Strong value in supported regions	Excellent price-performance	Less hand-holding for beginners
Akamai Cloud / Linode	Linux learning and predictable VPS use	Mature platform and free cloud firewall	Backups are a paid add-on

1. LightNode: Best for Flexible Global Testing

LightNode is a practical first choice when you want flexible billing or need a server in a less common region.

LightNode advertises hourly VPS billing, Linux and Windows support, quick deployment, NVMe storage, and more than 40 global locations. That makes it useful for testing latency, learning server administration, running bots, or deploying a small regional application without committing to a long contract.

Why beginners may like it

Hourly billing is useful for short experiments
Many global locations
Linux and Windows images
Simple VPS deployment workflow
Suitable for websites, APIs, bots, VPNs, and remote desktops

What to watch

Confirm bandwidth and backup costs before deploying
Delete unused instances instead of only shutting them down
Choose the closest useful region rather than the most unusual one

Best for: beginners who want global region flexibility and short-term testing.

👉 Visit LightNode

2. DigitalOcean: Best Overall Developer Experience

DigitalOcean calls its virtual machines Droplets. It is one of the easiest platforms for a beginner developer to understand because the dashboard, documentation, product names, and deployment workflow are relatively clear.

DigitalOcean also has a large tutorial library covering Ubuntu, Nginx, Docker, databases, DNS, firewalls, and application deployment. This can save a new user significant troubleshooting time.

Why beginners may like it

Clean control panel
Extensive technical documentation
Cloud firewalls and monitoring tools
Snapshots and backup options
Easy path from one Droplet to managed databases and storage

What to watch

Backups and managed products can add to the bill
A simple VPS can become a larger cloud stack quickly
Check outbound transfer limits for bandwidth-heavy projects

Best for: developers who value clear documentation and a polished dashboard.

👉 Visit DigitalOcean

3. Vultr: Best for Fast Deployment Across Many Regions

Vultr offers standard cloud compute, optimized compute, bare metal, GPU products, storage, snapshots, automatic backups, cloud-init, and optional DDoS protection.

For a beginner, the standard Cloud Compute product is normally enough. You do not need optimized compute or bare metal for a first website.

Why beginners may like it

Fast instance provisioning
Broad data center selection
Snapshots and automatic backup options
Simple API and cloud-init support
Room to move into more powerful infrastructure later

What to watch

Do not choose a specialized compute plan unless your workload needs it
Automatic backups and some protection features can cost extra
A snapshot is not a replacement for an independent application backup

Best for: users who want fast deployment and broad region coverage.

👉 Visit Vultr

4. Hetzner Cloud: Best Price-Performance in Supported Regions

Hetzner Cloud is well known for strong CPU, RAM, and storage value. Its cloud console supports server images, SSH keys, private networks, firewalls, volumes, snapshots, backups, cloud-init, and server resizing.

Hetzner's documentation states that automatic backups are created daily and stored in seven rotating backup slots when the backup service is enabled. Manual snapshots remain until you delete them.

Why beginners may like it

Strong resource value
Straightforward cloud server products
Cloud firewalls and private networking
Daily backups and manual snapshots
Good choice for Linux, Docker, and self-hosted applications

What to watch

Region selection is more limited than some global providers
Account verification can be strict
Support expects users to handle normal Linux administration
Attached volumes require their own backup strategy

Best for: cost-conscious users near a supported Hetzner region who are willing to learn Linux administration.

👉 Visit Hetzner Cloud

5. Akamai Cloud / Linode: Best Mature Linux VPS Platform

Akamai Cloud / Linode is a mature developer hosting platform. Linode compute instances support common Linux distributions, Cloud Manager, CLI and API management, monitoring, private networking, and reusable deployment scripts.

A particularly useful beginner feature is the Linode Cloud Firewall, which Akamai documents as available at no additional charge. Automated backups are available as a paid add-on.

Why beginners may like it

Long-established Linux VPS workflow
Clear compute plan structure
Free cloud firewall service
Monitoring and DNS tools
Strong API, CLI, Terraform, and documentation options

What to watch

Automated backups are an extra service
Some pages now use Akamai Cloud branding while users still call the product Linode
Advanced networking features are unnecessary for a first server

Best for: users who want a mature Linux-focused platform with a predictable path into infrastructure automation.

👉 Visit Akamai Cloud / Linode

Which Provider Should a Complete Beginner Choose?

Use this simple decision guide:

Choose LightNode if you want hourly billing and a wide choice of global regions.
Choose DigitalOcean if documentation and dashboard simplicity are your priorities.
Choose Vultr if you want fast deployment and many infrastructure options.
Choose Hetzner Cloud if price-performance is most important and its regions work for you.
Choose Akamai Cloud / Linode if you want a mature Linux VPS platform and free cloud firewall controls.

The provider matters, but your first server setup matters more. A well-secured small VPS is better than a large server with password-only root access and no backups.

Step 1: Create an SSH Key on Your Computer

SSH keys are safer than reusable passwords.

On macOS, Linux, or recent Windows versions with OpenSSH, run:

ssh-keygen -t ed25519 -C "cloud-server"

Press Enter to accept the default path. Add a passphrase when prompted.

Your public key is normally stored at:

~/.ssh/id_ed25519.pub

Display it:

cat ~/.ssh/id_ed25519.pub

Copy the entire output and add it to the provider dashboard before creating the server.

Never upload or share the private file:

~/.ssh/id_ed25519

Step 2: Deploy a Small Ubuntu Server

In the provider dashboard:

Choose Ubuntu 24.04 LTS.
Select the region closest to your users.
Choose 1-2 vCPU and 1-2 GB RAM.
Add your SSH public key.
Enable a provider firewall if available.
Decide whether to enable automatic backups.
Give the server a clear name such as learning-web-01.
Create the instance and copy its public IP address.

Do not install a marketplace image for your first Linux lesson. A clean Ubuntu image teaches you more and creates fewer unknown settings.

Step 3: Connect with SSH

Replace 203.0.113.10 with the real server IP:

ssh root@203.0.113.10

The first connection asks you to confirm the server fingerprint. Type:

yes

If the SSH key is configured correctly, you will enter the server without typing the root password.

Step 4: Update Ubuntu

Run:

apt update
apt upgrade -y
apt install -y curl git unzip ufw fail2ban

Reboot if the system installed a new kernel:

reboot

Wait a minute, then reconnect.

Step 5: Create a Non-Root Administrator

Create a user named deploy:

adduser deploy
usermod -aG sudo deploy

Copy the root SSH key configuration:

rsync --archive --chown=deploy:deploy ~/.ssh /home/deploy

Open a second terminal and test the new account before changing SSH settings:

ssh deploy@203.0.113.10

Then verify sudo:

sudo whoami

The output should be:

root

Do not close your original root session until the new user works.

Step 6: Harden SSH

Create a separate SSH configuration file:

sudo nano /etc/ssh/sshd_config.d/99-hardening.conf

Add:

PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

Check the SSH configuration:

sudo sshd -t

If the command returns no output, reload SSH:

sudo systemctl reload ssh

Open another terminal and confirm that ssh deploy@SERVER_IP still works.

Step 7: Configure the Firewall

Allow SSH before enabling UFW:

sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable

Check the rules:

sudo ufw status verbose

For a normal website, public inbound ports should generally be limited to:

22/tcp for SSH
80/tcp for HTTP
443/tcp for HTTPS

If the provider also has a cloud firewall, configure the same ports there. The provider firewall filters traffic before it reaches Ubuntu, while UFW protects the operating system itself.

Step 8: Install Nginx and Publish a Test Website

Install Nginx:

sudo apt install -y nginx
sudo systemctl enable --now nginx

Create a web directory:

sudo mkdir -p /var/www/first-cloud-site
sudo chown -R deploy:deploy /var/www/first-cloud-site

Create a simple page:

nano /var/www/first-cloud-site/index.html

Add:

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>My First Cloud Server</title>
  </head>
  <body>
    <h1>My first cloud server is working.</h1>
    <p>This page is served by Nginx on Ubuntu.</p>
  </body>
</html>

Create the Nginx server block:

sudo nano /etc/nginx/sites-available/first-cloud-site

Add:

server {
    listen 80;
    listen [::]:80;

    server_name _;
    root /var/www/first-cloud-site;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

Enable the site:

sudo ln -s /etc/nginx/sites-available/first-cloud-site /etc/nginx/sites-enabled/
sudo rm /etc/nginx/sites-enabled/default
sudo nginx -t
sudo systemctl reload nginx

Open the server IP in a browser:

http://203.0.113.10

You should see your test page.

Step 9: Connect a Domain and Enable HTTPS

At your DNS provider, create an A record:

Type	Name	Value
A	`@`	Your server IPv4 address

Optionally create:

Type	Name	Value
CNAME	`www`	Your root domain

Update the Nginx configuration:

server_name example.com www.example.com;

Test and reload:

sudo nginx -t
sudo systemctl reload nginx

Install Certbot:

sudo apt install -y certbot python3-certbot-nginx

Request a certificate:

sudo certbot --nginx -d example.com -d www.example.com

Test automatic renewal:

sudo certbot renew --dry-run

Do not run Certbot until the domain resolves to the server and port 80 is reachable.

Step 10: Configure Backups

Use more than one backup layer.

Provider Backup

Enable automatic provider backups if the project matters. This is convenient for recovering an entire instance.

Manual Snapshot

Create a snapshot before:

upgrading the operating system
changing disk partitions
migrating the application
performing a major database upgrade

Snapshots are useful recovery points, but they are not a complete backup strategy.

Off-Server Application Backup

Create an archive:

sudo tar -czf /tmp/first-cloud-site-$(date +%F).tar.gz /var/www/first-cloud-site

Copy it to your computer:

scp deploy@203.0.113.10:/tmp/first-cloud-site-2026-06-09.tar.gz .

For databases, create database-aware dumps using tools such as pg_dump or mysqldump. Copy important backups to another provider or your local machine.

Step 11: Add Basic Monitoring

Check resource usage:

free -h
df -h
uptime

Install htop:

sudo apt install -y htop
htop

Check failed services:

systemctl --failed

Check Nginx:

systemctl status nginx
journalctl -u nginx --since today

Check failed SSH attempts:

sudo journalctl -u ssh --since today

Provider monitoring can show CPU, bandwidth, and availability, but application logs still need to be checked inside the server.

Step 12: Understand How Billing Stops

This is a common beginner mistake:

Powering off a cloud server usually does not stop all charges.

The provider may continue reserving the virtual disk, IP address, backups, or other resources.

When your experiment is finished:

Download any files you need.
Take a final backup if necessary.
Delete the instance from the provider dashboard.
Delete unused snapshots, volumes, and reserved IPs.
Check the billing page for remaining resources.

Always read the confirmation screen before deleting a server. Deletion is normally permanent.

A Practical 7-Day Learning Plan

Day 1

Create a small Ubuntu server and connect with SSH.

Day 2

Create a sudo user, disable root login, and configure UFW.

Day 3

Install Nginx and publish a static page.

Day 4

Connect a domain and enable HTTPS.

Day 5

Deploy a small Node.js, Python, or Docker application.

Day 6

Create a provider snapshot and an off-server backup.

Day 7

Inspect logs and resource usage, then rebuild the server from the beginning.

Rebuilding is important. The first deployment teaches commands; the second teaches understanding.

Common Beginner Mistakes

Buying a large server before defining the workload
Choosing a distant region only because it is cheaper
Using password-only root login
Opening every firewall port
Exposing a database directly to the public internet
Running an application manually instead of using systemd or a process manager
Treating snapshots as the only backup
Forgetting to update Ubuntu
Ignoring provider billing for stopped resources
Deleting a server before testing the backup

Final Recommendation

For a complete beginner, the best first project is not a production business website. It is a disposable learning server with one clear goal.

Choose a small Ubuntu instance, add an SSH key, publish one page with Nginx, secure the server, connect a domain, make a backup, and then rebuild it.

Among the five providers:

LightNode is strong for hourly testing and global locations.
DigitalOcean offers the easiest documentation-driven learning path.
Vultr is useful for broad region coverage and fast deployment.
Hetzner Cloud offers excellent value where its regions fit.
Akamai Cloud / Linode provides a mature Linux-focused platform.

The right provider is the one that lets you practice safely without creating billing or operational complexity you do not yet need.