---
title: Cloud Hosting
description: "Resources from a pool of servers that can scale. Flexible, but cost and complexity need to be controlled."
canonical: https://penasihathosting.com/en/hosting-wiki/cloud-hosting
type: wiki
locale: en
updated: 2026-10-29
author: Willya Randika
---

# Cloud Hosting

## Overview

- **Summary:** Resources from a pool of servers that can scale. Flexible, but cost and complexity need to be controlled.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

Cloud hosting provides compute, storage, and networking from a pool of provider-managed servers. You are not tied to one physical machine. Resources can be added, removed, or moved, and services such as load balancers and managed databases are available as separate components.

## How it differs from a VPS

A VPS is usually one virtual machine with fixed resources. Cloud hosting is broader. Instances can be created from images, disks can be attached and detached, and multiple instances can sit behind a load balancer.

But cloud is not automatically highly available. If you run one instance without replication, an instance failure still takes the service down.

## Common components

A small architecture might use a load balancer with a health check, two application instances, a managed database, object storage for media, and a CDN. With two instances behind health checks, one can restart without taking the service down.

On AWS, the components could be an ALB, two `t4g.small` instances, RDS `db.t4g.micro`, S3, and CloudFront. Check `aws cloudwatch get-metric-statistics` for CPU and `aws s3 sync` for backups. Set a budget alert at, say, 80 percent of $100 per month, and tag resources by project.

## Costs to watch

Cloud bills compute by the hour or minute, storage by the GB, and often egress, which is data leaving the network. Egress can become the largest line item when serving video or large files. Old snapshots, idle public IPs, and unused load balancers are also billed.

Use budget alerts, tag resources, and stop test instances. For stable workloads, cloud can be more expensive than a VPS. For spiky workloads, elasticity can save money.

## Common mistakes

Assuming cloud is always faster is an expensive assumption. Latency depends on region, network, and architecture. Two instances without correct health checks can still send traffic to a dead server.

Storing backups in the same region is risky when the region fails. Vendor lock-in also matters when using highly specific managed services. Without a spending cap, a traffic spike or misconfiguration can produce a large bill.

Cloud hosting often uses a [load balancer](/en/hosting-wiki/load-balancer), [object storage](/en/hosting-wiki/object-storage), and [anycast](/en/hosting-wiki/anycast). Compare it with [shared vs VPS vs dedicated](/en/hosting-wiki/shared-vps-dedicated) before choosing.

## FAQ

<Accordion>
  <AccordionItem title="Is cloud hosting suitable for a small site?">
    It can be, but it is often overkill. A small site with stable traffic is usually cheaper and simpler on shared hosting or a VPS.
  </AccordionItem>
  <AccordionItem title="Is cloud hosting automatically highly available?">
    No. You need multiple instances, a load balancer, a redundant database, and failover testing. One instance is still a single point of failure.
  </AccordionItem>
  <AccordionItem title="What is egress?">
    The charge for data leaving the provider's network, such as images or video sent to visitors. Check the rate before choosing.
  </AccordionItem>
</Accordion>