Cloud Computing Basics

Introduction

Cloud Computing Basics introduces you to the main ideas behind modern cloud services and shows how they appear in real workplaces. The course is designed for apprentices, trainees, and vocational students who use digital tools, support users, administer systems, develop applications, or work with connected machines and business data.

In simple terms, cloud computing means using computing resources over a network when you need them instead of owning and operating every server, storage device, database, or application yourself. A cloud provider can supply resources such as processing power, storage, networking, databases, and software. You usually provision these resources through a web portal, command-line tool, or application programming interface.

A widely used reference is the NIST cloud model. It describes five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. These ideas help you distinguish a true cloud service from ordinary remote hosting.

Cloud computing can help organizations start services quickly, scale resources up or down, and reduce the need for large upfront hardware purchases. However, cloud use is not automatically cheaper, safer, or more reliable. Good results depend on correct configuration, security, monitoring, backup, cost control, and clear responsibilities.

Learning Goals

After working through this aiMOOC, you should be able to explain the basic cloud model, distinguish major service and deployment models, connect cloud services with workplace use cases, describe the role of virtualization, recognize important security responsibilities, estimate basic cost drivers, and plan a simple cloud solution for a vocational scenario.

You should also be able to discuss cloud choices with colleagues using clear technical language. This is useful in IT support, system administration, software development, industrial digitalization, office administration, logistics, media work, retail, healthcare technology, and many other professions.

What Makes a Service a Cloud Service?

Cloud computing is more than putting a server on the Internet. A cloud service normally combines several characteristics that make computing resources flexible and manageable.

On-demand self-service means you can request resources yourself without waiting for a technician at the provider to install hardware manually. For example, an authorized trainee may create a test virtual machine from a portal.

Broad network access means services are available over networks through standard mechanisms. A user may work from a laptop, workstation, tablet, or other approved device.

Resource pooling means providers combine physical and virtual resources so that many customers can use the infrastructure efficiently. Customers are logically separated even when underlying hardware is shared.

Rapid elasticity means resources can grow or shrink quickly. A web shop can add capacity during a sales campaign and reduce it afterward.

Measured service means usage can be monitored and often billed according to consumption. This makes metering, budgets, alerts, and resource cleanup important workplace skills.

A useful rule is: cloud resources feel flexible to the user because much of the physical complexity is hidden behind automation and service interfaces.

From Data Center to Cloud

A traditional data center contains physical servers, storage systems, network equipment, power supplies, cooling, cabling, and security controls. An organization that owns this equipment is responsible for buying, installing, operating, patching, replacing, and protecting it.

Cloud providers operate large-scale infrastructure and expose parts of it as services. The customer no longer handles every physical component, but the customer still has important responsibilities. Those responsibilities depend on the selected service model.

For vocational practice, think of the difference between owning a complete workshop and renting a specialized service. Ownership gives you more control but also more maintenance work. A managed service removes some maintenance tasks, but you must understand what the provider does and what remains your job.

Typical Workplace Uses

A small business may store documents in a managed cloud drive, run email as a cloud application, host a website on a managed platform, back up files to object storage, or run a virtual server for a specialist application.

A training center may use cloud collaboration tools, virtual labs, learning platforms, and shared storage. A manufacturing company may collect sensor data, operate dashboards, or connect branch locations to centrally managed services. A software team may create temporary test systems instead of purchasing new hardware for every project.

These examples show that cloud computing is not one product. It is a way of delivering many kinds of IT resources as services.

Cloud Service Models

The three classic service models are Infrastructure as a Service, Platform as a Service, and Software as a Service. They differ mainly in how much of the technology stack the provider manages for you.

Infrastructure as a Service

Infrastructure as a Service (IaaS) gives you fundamental computing resources such as virtual machines, storage, and networking. The provider manages the physical data center, physical servers, and virtualization layer. You normally manage the operating system, applications, data, many network settings, and much of the security configuration inside the virtual environment.

A common IaaS task is creating a virtual server for a line-of-business application. You choose a machine size, operating system image, storage, network, and access rules. You must also plan updates, accounts, backups, monitoring, and shutdown procedures.

IaaS offers flexibility and control, but that freedom brings responsibility. An unused virtual machine can continue to generate cost, and an incorrectly configured network rule can create a security risk.

Platform as a Service

Platform as a Service (PaaS) provides a managed environment for running or developing applications. The provider manages more of the underlying operating system, runtime, scaling infrastructure, and maintenance. You focus more on application code, configuration, and data.

For example, a trainee developer might deploy a web application to a managed application platform instead of installing and patching a complete web server. The team can spend more time on the application while the provider handles much of the platform operation.

PaaS can speed up development, but you still need to understand service limits, identity settings, data protection, logging, and cost.

Software as a Service

Software as a Service (SaaS) gives you a ready-to-use application, usually through a web browser or client app. The provider operates the application and most of the underlying technology. Examples include hosted email, collaboration platforms, customer relationship management systems, and online office tools.

SaaS usually reduces technical maintenance for the customer, but users and administrators still have responsibilities. These include account security, access permissions, data handling, device security, configuration, and correct use of the service.

A practical way to remember the models is this: with IaaS you manage more, with PaaS you manage less infrastructure, and with SaaS you mainly use and configure the finished application.

Cloud Deployment Models

A deployment model describes how cloud infrastructure is organized and who it serves.

Public cloud uses provider-operated infrastructure offered to many customers. Customers share the provider's large resource pool while their systems and data remain logically separated.

Private cloud is dedicated to one organization. It can be operated by the organization or another party. It may offer more direct control over infrastructure and policy, but the organization usually carries more operating responsibility.

Hybrid cloud combines different cloud environments, such as private infrastructure and public cloud services, with connections and processes that allow workloads or data to work across them.

Community cloud is shared by organizations with common requirements or concerns. It is less common in everyday vocational examples but remains part of the classic NIST deployment model.

Multi-cloud is a common modern term for using services from more than one cloud provider. It can reduce dependence on one provider or match different services to different needs, but it also increases operational complexity.

Choosing a Deployment Model

Do not choose a model only because it is popular. Start with the workload. Ask what data is involved, who needs access, which laws or company rules apply, how quickly the service must recover after failure, how much control is required, and which skills the organization has.

A small training company may use public SaaS for collaboration. A hospital supplier may need stricter controls for sensitive data. A manufacturer may keep a latency-sensitive production system on-site while sending selected analytics data to a public cloud. The best architecture follows requirements rather than fashion.

Virtualization: A Key Enabling Technology

Virtualization creates a software-based version of computing resources. One physical server can run several isolated virtual machines, each with its own operating system and applications. A hypervisor allocates physical resources such as CPU time, memory, storage, and networking to these virtual machines.

Virtualization and cloud computing are related but not identical. A company can use virtual machines in its own server room without having a cloud. Cloud computing adds service characteristics such as self-service provisioning, resource pooling, elasticity, and measured use.

Virtualization improves hardware utilization and makes systems easier to create, copy, isolate, and move. Cloud platforms build on these ideas and add automation at a much larger scale.

Storage in the Cloud

Cloud storage is a major cloud use case. Three common forms are object storage, block storage, and file storage.

Object storage stores data as objects with metadata. It is often used for backups, images, videos, logs, archives, and data lakes. You usually access it through web-based interfaces or APIs.

Block storage provides storage volumes that behave more like disks attached to virtual machines. It is useful for operating systems, databases, and applications that expect disk-like storage.

File storage provides shared folders and familiar file-system access. It can support team shares, application data, and workloads that need standard file protocols.

When selecting storage, consider performance, durability, availability, access frequency, retention period, location, encryption, backup strategy, and data transfer charges. A cheap archive tier may be unsuitable for files that must be opened every few minutes.

Backup Is Not the Same as Sync

A synchronized folder helps keep current files consistent across devices, but synchronization can also spread accidental deletion, corruption, or malicious changes. A real backup strategy keeps protected copies that can be restored after a problem.

For important business data, use versioning or backup features where appropriate, define retention periods, control who can delete backups, and test restoration. A backup that has never been restored in a test is only an assumption.

Cloud Networking Basics

Cloud systems still depend on networking. Important concepts include IP addresses, subnets, DNS, routing, firewalls, gateways, load balancers, and private network connections.

A cloud network is often divided into smaller segments. Public-facing services should expose only the ports they need. Internal databases normally should not be directly reachable from the public Internet. Security groups, firewall rules, and network access lists can limit communication.

A load balancer distributes incoming traffic across multiple service instances. This can improve availability and make scaling easier. DNS translates human-readable names into network addresses. Private connectivity or a virtual private network can connect a workplace network to cloud resources.

For vocational troubleshooting, always check the whole path: client device, local network, DNS, Internet connection, cloud network rules, application endpoint, and service health.

Security and Shared Responsibility

Cloud security follows a shared responsibility model. The provider protects parts of the underlying service, while the customer protects the parts it controls. The exact boundary changes between IaaS, PaaS, and SaaS.

With IaaS, the customer usually has major responsibility for guest operating systems, applications, data, accounts, and network configuration. With PaaS, the provider manages more of the operating platform. With SaaS, the provider manages most of the application stack, but the customer still controls important areas such as users, permissions, data handling, and endpoint security.

Identity is a security boundary. Use individual accounts, strong authentication, multi-factor authentication, and the principle of least privilege. Remove access when a person changes role or leaves the organization.

Encryption protects data from unauthorized reading. Encryption in transit protects communication, while encryption at rest protects stored data. Encryption does not replace access control, backups, logging, or secure configuration.

Logging and monitoring help you detect failures, unusual activity, and policy violations. Important events can include failed logins, privilege changes, deleted resources, disabled security controls, and unexpected data transfers.

Never place passwords, API keys, or private credentials in public code repositories or shared documents. Use approved secret-management methods and follow workplace policies.

Reliability, Availability, and Recovery

Cloud providers build large infrastructures, but failures can still happen. Good design assumes that hardware, networks, software, and people can fail.

A region is generally a geographic area in which a provider operates cloud infrastructure. An availability zone is typically an isolated location within a region, designed so that services can be distributed across failure domains. Exact definitions vary by provider.

High availability may require multiple service instances, multiple zones, health checks, load balancing, redundant data, and tested recovery procedures. Simply moving one server to the cloud does not automatically make an application highly available.

Two useful recovery terms are Recovery Time Objective (RTO) and Recovery Point Objective (RPO). RTO describes how quickly a service should be restored. RPO describes how much recent data loss is acceptable, expressed as a time period.

A workplace team should know who declares an incident, where documentation is stored, how backups are restored, how users are informed, and how lessons are recorded afterward.

Cost and Consumption

Cloud services often use consumption-based pricing. This can reduce upfront capital spending, but it can also create unexpected bills if resources are oversized, left running, or used inefficiently.

Important cost drivers include compute time, storage capacity, storage class, database size, network data transfer, backup retention, monitoring data, licenses, and support plans. Some services charge for requests or operations as well as for storage or runtime.

A good technician treats cost as an operational signal. Use budgets, alerts, tags, naming standards, automatic shutdown where appropriate, and regular cleanup of unused resources. Compare the cost of cloud services with the full cost of on-premises systems, including hardware, electricity, maintenance, staff time, replacement cycles, and downtime risk.

Cloud cost optimization is not simply choosing the cheapest service. The goal is to meet requirements at an acceptable total cost.

A Practical Cloud Workflow

When you receive a workplace task such as "put this application in the cloud," do not start by clicking the first deployment button you see. Use a repeatable process.

Requirements analysis: Identify users, business purpose, performance needs, data sensitivity, legal requirements, budget, and recovery expectations.
Cloud service model: Decide whether SaaS, PaaS, or IaaS gives the right balance of control and management effort.
Identity and access management: Define who can administer, use, and audit the service.
Network security: Plan connectivity, public exposure, firewall rules, and private access.
Data management: Choose storage, encryption, retention, backup, and recovery methods.
Monitoring: Collect health, performance, security, and cost information.
Documentation: Record the architecture, settings, responsibilities, contacts, and recovery steps.

This workflow reflects professional practice: understand the requirement, reduce unnecessary risk, document decisions, and verify that the service works as intended.

Vocational Scenario: A Small Service Company

Imagine a small repair company with twenty employees. It needs shared documents, appointment scheduling, a customer portal, and backups. The company has one part-time IT technician and does not want to run a large server room.

For shared office documents, SaaS may be suitable because the provider manages the application. For the customer portal, PaaS may reduce server maintenance while allowing the developer to deploy custom code. If a legacy workshop application requires a specific operating system, IaaS may be appropriate. Backups may use object storage with retention and restricted deletion.

The company should also configure multi-factor authentication, role-based access, logging, tested recovery procedures, and cost alerts. This example shows why real cloud solutions often combine several service models.

Interactive Tasks

Quiz: Test Your Knowledge

Which characteristic lets a user provision resources without manual provider intervention? (On-demand self-service) (!Physical colocation) (!Manual procurement) (!Local-only access)

Which cloud service model normally gives the customer the most control over the operating system? (Infrastructure as a Service) (!Platform as a Service) (!Software as a Service) (!Community cloud)

Which service model provides a ready-to-use application to the customer? (Software as a Service) (!Infrastructure as a Service) (!Platform as a Service) (!Bare-metal hosting)

Which deployment model combines different cloud environments into one architecture? (Hybrid cloud) (!Public cloud) (!Private cloud) (!Object storage)

What does rapid elasticity allow a cloud service to do? (Scale resources quickly with demand) (!Remove all security duties) (!Guarantee zero downtime) (!Eliminate network traffic)

What is the main role of a hypervisor? (Allocate physical resources to virtual machines) (!Translate domain names) (!Encrypt every cloud file) (!Create user passwords)

Which storage type is commonly used for backups and large collections of files as objects? (Object storage) (!CPU cache) (!Printer memory) (!Firmware storage)

Which security practice adds a second verification factor to an account? (Multi-factor authentication) (!Resource pooling) (!Load balancing) (!Data compression)

What does an RTO describe? (The target time to restore a service) (!The allowed amount of storage) (!The number of user accounts) (!The speed of a processor)

Which action helps control cloud spending? (Set budgets and remove unused resources) (!Disable all monitoring) (!Keep every test system running) (!Use the largest service size by default)

Memory Game

Elasticity	Ability to scale resources with changing demand
Hypervisor	Software layer that manages virtual machines
SaaS	Ready-to-use software delivered as a service
Object storage	Storage organized around objects and metadata
Least privilege	Giving only the access required for a task
RPO	Maximum acceptable period of recent data loss

Drag and Drop

Match the correct terms.	Topic
Infrastructure as a Service	Customer manages the operating system and applications
Platform as a Service	Customer deploys applications without managing the underlying operating system
Software as a Service	Customer uses a finished provider-managed application
Hybrid cloud	Architecture combines different cloud environments
Measured service	Resource use is monitored and can support consumption-based billing

Match each cloud concept with the description that best fits its role in a workplace.

Crossword Puzzle

Elasticity	What cloud property allows capacity to grow or shrink with demand?
Hypervisor	What software layer manages virtual machines on physical hardware?
Datacenter	What facility contains servers, storage, networking, power, and cooling?
Encryption	What process protects information by making it unreadable without the proper key?
Multitenancy	What concept lets multiple customers share provider resources while remaining logically separated?
Provisioning	What process creates and configures computing resources for use?

LearningApps

Cloze Text

Cloud computing provides access to configurable computing resources over a

. A customer can request resources directly through

mechanisms. Cloud platforms can increase or reduce capacity through

. In the IaaS model, the customer normally manages the guest

. A managed application delivered to end users is called

. Virtual machines are commonly controlled by a

. Strong account protection should include

. A recovery plan should be tested by actually restoring a

. Cloud spending can be controlled by monitoring usage and setting a

.

Open-Ended Tasks

Easy

Cloud Vocabulary Poster: Create a one-page poster that explains cloud, SaaS, PaaS, IaaS, elasticity, and virtualization in your own words with simple workplace examples.
Cloud Service Interview: Interview a classmate or colleague about one cloud service they use at work or in training and record what problem it solves.
Workplace Cloud Inventory: Identify four digital services used in your training environment and classify each as local, SaaS, PaaS, IaaS, or unclear, explaining your reasoning.
Cloud Diagram: Draw a simple picture showing a user device, the Internet, a cloud service, and the underlying data-center resources, then label the data flow.

Standard

Service Model Comparison: Choose one business application and design three possible solutions using SaaS, PaaS, and IaaS, comparing control, maintenance effort, security duties, and likely skills required.
Backup Restore Test: In a safe training environment, create sample files, back them up using an approved method, delete one original file, restore it, and document every step and result.
Cloud Security Checklist: Build a checklist for a small company that covers identities, multi-factor authentication, least privilege, encryption, logging, backups, updates, and incident contacts.
Cost Estimate: Use a cloud provider's public calculator or training pricing page to estimate a small virtual server or storage workload, state your assumptions, and identify three factors that could change the cost.

Advanced

Cloud Migration Plan: Select a realistic legacy application and produce a migration plan that compares keeping it on-site, moving it to IaaS, redesigning it for PaaS, or replacing it with SaaS.
Resilient Architecture: Design an architecture for a customer portal that continues operating after one service instance fails, including load balancing, backup, monitoring, and recovery objectives.
Cloud Security Review: Examine a teacher-provided or sandbox cloud configuration, identify at least five security or governance risks, rank them by impact and likelihood, and propose corrections.
Cloud Project Video: Produce a short instructional video for new apprentices that demonstrates a complete cloud workflow from requirements and deployment to monitoring, cost control, backup, and documentation.

Learning Assessment

Architecture Decision: Given a small company's need for email, a custom web portal, and one legacy application, choose suitable service models for each workload and justify your choices using control, maintenance, security, and cost.
Shared Responsibility Analysis: Compare the customer's security duties in IaaS, PaaS, and SaaS for identities, data, operating systems, applications, and network controls, then explain where misunderstandings could create risk.
Failure Scenario: A cloud-hosted application becomes unavailable after a configuration change; create a troubleshooting sequence that separates local network, DNS, cloud network, application, identity, and provider-service causes.
Recovery Planning: A workshop can tolerate two hours of downtime and at most fifteen minutes of recent data loss; propose a backup and recovery design and explain how you would test it.
Cost and Governance Case: A training department's cloud bill doubles in one month; identify plausible technical and organizational causes, specify evidence you would inspect, and recommend controls that prevent recurrence.

Evidence of Learning

Knowledge evidence includes accurate explanations of cloud characteristics, service models, deployment models, virtualization, storage, networking, shared responsibility, reliability, recovery, and cost drivers.

Skill evidence includes the ability to classify workloads, choose suitable cloud models, apply identity and access controls, read basic architecture diagrams, plan backups, troubleshoot connectivity, monitor usage, and document technical decisions.

Product evidence can include a cloud architecture diagram, service comparison, restore-test report, cost estimate, security checklist, migration plan, troubleshooting record, or instructional video.

Transfer evidence appears when you can apply the same principles to a new workplace problem, explain trade-offs to non-specialists, identify risks before deployment, and revise a design when requirements change.

Good evidence is not only a correct final answer. It also shows a traceable process: requirements, assumptions, decisions, tests, results, and lessons learned.

OERs on the Topic

Useful open and public learning references include the Cloud computing article, the Virtualization article, and freely accessible introductory material from standards organizations and major cloud providers. When you use vendor documentation, separate general cloud principles from features that apply only to one provider.

Reference sources: NIST SP 800-145 for the classic cloud definition and models, Microsoft Learn for shared responsibility, and AWS documentation for an introductory description of on-demand cloud resources.

Linked Learning Areas

Cloud Computing Basics

Cloud computing connects technical knowledge with business decisions. In vocational education, it links networking, system administration, software development, cybersecurity, data management, project work, documentation, budgeting, and customer communication.

aiMOOC Projects

Diesen aiMOOC als Battle spielen: Englisch, Klasse 5-6, G-Niveau

Inhalte werden geladen ...

Mediathek wird aus dem Wiki geladen ...

Frag mich zum aktuellen Lerninhalt oder wähle eine kurze Hilfe.

Textmodus bereit

Sprache

English:Cloud Computing Basics