# Cloud Service Models

Cloud service models define which technology layers a provider operates and which responsibilities remain with the customer.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/cloud-service-models

> Infrastructure as a Service, Platform as a Service, and Software as a Service provide different levels of abstraction and operational control. Understanding these models helps engineers choose suitable services and identify who must secure, configure, patch, and maintain each part of a workload.

Practice exams covering Cloud Service Models: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner).

## 6 key aspects of Cloud Service Models

Cloud service models organize operational ownership by abstraction level while preserving customer responsibility for data, access, and secure configuration.

1. **Layer-based responsibility**: Identify ownership separately for infrastructure, operating systems, runtimes, applications, and data. This prevents assumptions such as treating provider-managed hardware as evidence that the provider also patches customer-installed software.
2. **Different levels of abstraction**: IaaS exposes infrastructure control, PaaS provides a managed application platform, and SaaS provides a complete application. Serverless functions further abstract execution infrastructure while leaving code and access controls with the customer.
3. **Service-dependent security boundaries**: Responsibility changes with the service and its operating mode. A customer patches an EC2 guest operating system, whereas AWS manages the underlying operating systems used by standard RDS and Lambda.
4. **Persistent customer obligations**: Customers retain responsibility for their data, access decisions, and customer-controlled security settings. Managed services do not automatically make application code secure or prevent overly permissive access.
5. **Control versus operational effort**: Greater infrastructure control usually brings more maintenance and security work. Greater provider management reduces that work but can limit customization, software choices, and portability.
6. **Configuration and lifecycle awareness**: Managed services still require decisions about supported versions, maintenance settings, backups, and recovery objectives. Check the responsibility boundary for the exact service configuration instead of relying only on an IaaS, PaaS, or SaaS label.

## Cloud services for Cloud Service Models

Amazon EC2, Amazon RDS, and AWS Lambda show how one application can combine different responsibility boundaries. An application might run its web tier on EC2, store relational data in RDS, and process events with Lambda. Engineers patch the EC2 guest operating system but do not administer the underlying operating systems for standard RDS or Lambda. They still secure application code, database access, function permissions, and data flows across all three. Reviewing responsibilities component by component avoids assigning the entire application a single service-model label and overlooking maintenance or security obligations.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon EC2 illustrates IaaS: AWS operates the physical infrastructure and virtualization layer, while customers manage the guest operating system and installed applications. Customers must patch their instances, restrict network access, and configure workload permissions.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Standard Amazon RDS deployments illustrate managed database responsibility: AWS operates the underlying infrastructure and handles operating-system and database software maintenance. Customers manage database access, schemas, data, network exposure, and settings such as backup retention and maintenance windows; Amazon RDS Custom has a different responsibility boundary.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Lambda illustrates serverless function execution, with AWS managing execution infrastructure and the underlying operating system. Customers secure function code, dependencies, execution roles, triggers, and data, and must account for runtime lifecycle requirements and container-image updates where applicable.

## Cloud Service Models exam questions

Real practice exam questions on Cloud Service Models, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company is deploying an application with a security requirement to install its own host-based monitoring agent and directly configure guest operating system security settings. The company is willing to take on additional maintenance work to retain this control. Which deployment approach meets these requirements under the AWS shared responsibility model?

**Correct answer:** Use Amazon EC2 and have the company install the monitoring agent, configure guest operating system settings, and maintain the guest operating system.

**Explanation:** Amazon EC2 provides customer control of the guest operating system. The company can install host-based agents and configure operating system security, but it is also responsible for maintaining and patching that operating system.

## Practice Cloud Service Models in a full exam

Questions on Cloud Service Models in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 1 question

## What is Cloud Service Models

Cloud service models describe how responsibility for a technology stack is divided between a cloud provider and its customer. The stack includes physical facilities, hardware, virtualization, operating systems, runtimes, applications, and data. Moving toward a more managed service generally transfers more infrastructure operations to the provider, but it does not eliminate customer responsibility for security or correct configuration.

Infrastructure as a Service, or IaaS, provides fundamental resources such as virtual machines, storage, and networking. The provider operates the physical infrastructure and virtualization layer, while the customer manages the guest operating system and installed software. For example, with Amazon EC2, AWS maintains the underlying hosts and hypervisor. The customer patches the instance operating system, updates application dependencies, configures security groups, and manages identities, application security, and data protection.

Platform as a Service, or PaaS, provides a managed environment for deploying applications without directly administering every underlying infrastructure layer. The provider typically operates the operating system and platform components, while the customer controls application code, data, and permitted configuration. Managed databases apply a similar division of responsibility. With standard Amazon RDS deployments, AWS manages the underlying operating system and database software maintenance, while customers manage database users, permissions, schemas, queries, network access, and backup retention settings. Customers must also plan maintenance windows, supported engine versions, and required upgrades; managed maintenance does not mean that every operational decision disappears.

Software as a Service, or SaaS, delivers a complete application that customers use and configure rather than build and operate. The provider manages the application stack, but customers still manage responsibilities such as user access, tenant settings, data classification, and appropriate use. A provider-operated application can still expose sensitive information if a customer grants excessive access or configures sharing incorrectly.

Serverless computing provides another useful abstraction, often described as Function as a Service for function execution. With AWS Lambda, AWS manages the execution infrastructure and underlying operating system. Customers remain responsible for function code, dependencies, execution-role permissions, triggers, secrets, and data handling. For managed runtimes, runtime updates follow Lambda's runtime management settings and support lifecycle. For container-image functions, customers must rebuild and deploy updated images, including updated runtime components and dependencies.

These models involve trade-offs rather than a simple ranking. IaaS offers extensive operating-system control and software flexibility but requires more patching and administration. Managed platforms and serverless services reduce infrastructure work but impose constraints on supported versions, execution environments, configuration, and portability. SaaS removes much application-operation work while offering less control over application implementation. Actual service capabilities and contractual responsibilities matter more than assigning every product a rigid model label.

The AWS shared responsibility model describes AWS as responsible for security of the cloud and customers as responsible for security in the cloud. The boundary shifts with the service: guest operating-system patching belongs to the customer on EC2, but AWS manages the underlying operating systems for standard RDS and Lambda. Data classification, access decisions, and secure customer-controlled configuration remain customer responsibilities across these examples. For exam scenarios and architecture reviews, identify the specific component and service rather than assuming that either party owns all security. Service models also differ from deployment models: public, private, and hybrid cloud describe deployment arrangements, not which stack layers the provider manages.

## Learn Cloud Service Models in lessons

1 short lesson on Cloud Service Models in 1 certification course.

- CLF-C02: Cloud Service Models: abstraction and management boundaries (Premium), https://app.blowstack.com/lessons/cloud-service-models-abstraction-and-management-boundaries-clf-c02
