Introduction to Cloud Computing Concepts

Cloud computing is a model for delivering on-demand IT resources over the internet. Instead of buying, owning, and maintaining physical data centres and servers, you access technology services from a cloud provider as you need them. Think of it as renting a house instead of buying one: you avoid the big upfront cost, you do not have to fix the roof, and you can move out whenever you want. The key characteristics, defined by the National Institute of Standards and Technology (NIST), are essential to understand for the CV0-004 exam. They are: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service.

On-demand self-service means you can provision computing resources like virtual machines (VMs) or storage without needing to talk to a human at the provider. You log into a web portal, click a few buttons, and the resource is ready in minutes. Broad network access simply means those resources are available over the network — typically the internet — and can be accessed from any device: a laptop, a phone, a tablet. Resource pooling is the provider's ability to serve many customers from the same physical hardware, using something called multi-tenancy. Multi-tenancy means your virtual server lives on the same physical machine as other customers' virtual servers, but your data is completely isolated from theirs. This is what drives down costs: the provider buys one big server and splits it among hundreds of customers.

Rapid elasticity is the ability to scale resources up or down automatically based on demand. If your website gets a sudden spike in visitors, cloud resources can add more virtual servers to handle the load, and then remove them when traffic drops. This is often called auto-scaling. Measured service means that usage is metered, like a utility bill. You pay for exactly how much CPU time, storage space, or network bandwidth you consume. Cloud providers can be divided into three main service models: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

IaaS gives you the most control. You rent virtual machines, storage, and networks, but you are responsible for managing the operating system, applications, and middleware. It is like renting an empty apartment: you bring your own furniture and you paint the walls yourself. PaaS provides a platform to develop and run applications without worrying about the underlying infrastructure. The provider manages the operating system, runtime, and middleware. You just deploy your code. This is like renting a fully furnished office: you bring your laptop and your work files, but the desks, chairs, and internet connection are already set up. SaaS delivers a complete application that you access through a browser. You do not manage anything; you just use the software. Examples include Gmail, Microsoft 365, and Salesforce.

Another critical concept is the deployment model. The three primary models are public cloud, private cloud, and hybrid cloud. A public cloud means the provider's infrastructure is shared among many different customers over the public internet. A private cloud is used exclusively by a single organisation, either hosted on-premises or by a third party. A hybrid cloud combines both, allowing data and applications to move between them. For example, a bank might keep sensitive customer data in a private cloud but use public cloud resources for less sensitive development work.

Why does cloud computing exist? It replaces the traditional model where every company ran its own data centre. Traditional data centres required huge upfront capital expenditure (CAPEX) to buy servers, networking gear, and cooling systems. They also needed a team of IT staff to patch, maintain, and troubleshoot hardware. This was wasteful: most servers sat at 15-30% utilisation because you had to buy enough capacity for peak demand, even though most of the time you needed far less. Cloud computing flips this model to operational expenditure (OPEX): you pay as you go, and the provider handles utilisation by pooling resources across thousands of customers. This is known as economies of scale, where the provider's massive purchasing power and efficiency make computing cheaper for everyone.

Finally, the concept of the shared responsibility model is vital. In cloud computing, security and management are a partnership. The cloud provider is responsible for security of the cloud — protecting the physical data centres, networking infrastructure, and hypervisors. The customer is responsible for security in the cloud — configuring firewalls, managing identity and access, and patching their own operating systems in IaaS. In PaaS and SaaS, the provider takes on more of that responsibility. The CV0-004 exam will test your understanding of this split, especially for scenarios involving compliance and data protection.

Imagine a mid-sized e-commerce company called 'Urban Quill' that sells handmade notebooks and pens. Up until last year, Urban Quill ran its own on-premises data centre in a small room at its office. The company had a rack of servers, a storage area network (SAN), and a firewall. The IT team of two people spent their days patching servers, replacing failed hard drives, and managing backups. Then the company launched a new product line, and a viral TikTok video drove 50,000 visitors to the website in one hour. The on-premises servers could not handle the load; the website crashed, and Urban Quill lost thousands of pounds in sales.

The company decided to migrate to the cloud. Here is what the IT team actually did, step by step. First, they chose Amazon Web Services (AWS) as their provider and set up a cloud account. They used the AWS Management Console to create a virtual private cloud (VPC), which is a logically isolated section of the AWS cloud where they define their own IP address range and subnets. This is the virtual equivalent of plugging a cable into their network. Next, they launched a series of Amazon EC2 instances, which are virtual machines. They selected an operating system (Ubuntu Linux), chose a VM size with 4 virtual CPUs and 16 GB of RAM, and configured a security group — think of it as a virtual firewall — to allow only HTTP and HTTPS traffic from the internet.

Then they installed their web application software on the virtual machines and connected them to an Elastic Load Balancer (ELB). The load balancer distributes incoming traffic across multiple VMs automatically. Urban Quill also set up auto-scaling: they configured a rule that says if the average CPU utilisation across all VMs exceeds 70% for five minutes, the cloud automatically spins up two additional EC2 instances. When traffic drops below 30% utilisation, it automatically terminates the extra instances. This eliminated the crashing problem entirely. They moved their database to Amazon RDS (Relational Database Service), a managed PaaS solution. Instead of patching the database server themselves, they chose a maintenance window and let AWS apply updates automatically. They also enabled automated backups with point-in-time recovery, which means they can restore the database to any second within the last 35 days.

The key work the IT team now does is no longer about racking servers. Their daily tasks shifted to:\ - Configuring IAM (Identity and Access Management) policies to control who can launch or terminate instances.\ - Setting up CloudWatch alarms to monitor instance health and cost anomalies.\ - Writing Infrastructure as Code (IaC) templates using AWS CloudFormation to define all resources in a reusable, version-controlled text file.\ - Reviewing cost reports to optimise reservations and right-size instances.\ The result: Urban Quill saved 40% on IT costs in the first year, saw zero downtime during the next viral event, and the two IT staff now focus on developing new features instead of replacing dead hard drives.