Infrastructure as a service¶
A cloud service model in which a provider supplies API-controlled compute, storage, networking, virtualization, and physical facilities on demand while the customer manages operating systems, deployed software, data, identities, and configuration under a shared-responsibility boundary.
Core Idea¶
Infrastructure as a service (IaaS) is a cloud service model in which a provider operates facilities, physical compute, storage, networking, and virtualization while customers provision infrastructure primitives through a control plane and manage guest operating systems, applications, identities, configuration, and data under a shared-responsibility agreement. The defining feature is the management boundary. The defining feature is the management boundary.
Scope of Application¶
IaaS is used for enterprise migration, elastic web services, development environments, disaster recovery, high-performance workloads, data platforms, network labs, regulated infrastructure, and hybrid-cloud architectures. Use it with provider/service/version, regions/zones and tenancy, resource types/quotas, isolation, images and patch ownership, virtual networking and identities, storage/durability/encryption, backup and tested recovery, availability/support SLA, observability and incident duties, scaling/metering/cost controls, compliance/residency, dependencies and exit/deletion plan, plus an explicit responsibility matrix and boundary from PaaS, SaaS, colocation, and virtualization alone.
- Compute. Provisions virtual or bare-metal instances.
- Storage. Attaches object/block/file primitives.
- Networking. Defines virtual networks and connectivity.
- Recovery. Replicates resources across failure domains.
- Governance. Controls identity, cost, compliance, and lifecycle.
Clarity¶
Report provider/service/version, tenancy and regions/zones, resource primitives and quotas, hypervisor or isolation assumptions, images/OS and patch ownership, networks/firewalls/load balancers, identities and keys, data/storage/durability/encryption, backup/recovery objectives and tests, availability/support SLA, monitoring/logging/incident duties, scaling automation, metering/pricing, compliance/data residency, dependencies, portability and exit/deletion plan, and shared-responsibility matrix. The closest near miss sets the boundary: Platform as a service is nearest: it manages more of the runtime and deployment platform, whereas IaaS typically leaves the guest OS and stack to the customer.
Manages Complexity¶
IaaS hides physical operations behind programmable primitives but exposes a new distributed control plane, contract, responsibility split, and lifecycle that customers must manage coherently. The central elasticity–cost control tradeoff is this: Resources scale quickly while idle or runaway capacity accrues charges. A second provider abstraction–customer accountability tension matters because Physical burden falls away while guest/data/configuration duties remain.
Abstract Reasoning¶
Use three linked moves: define workload and risk requirements; map each component to provider- or customer-managed responsibility; design identity, network, data, availability, and recovery controls. As a collapse test, the classification changes when a managed service shifts the control and responsibility boundary; provider branding alone cannot settle it. A fourth check is to automate versioned provisioning and observe cost/performance/security.
Knowledge Transfer¶
Infrastructure primitives transfer among cloud providers only imperfectly: APIs, network models, identities, images, managed adjuncts, pricing, regions, and responsibility boundaries must be remapped. No canonical parent prime is currently asserted; broader structural comparisons remain related-prime analogies until separately adjudicated in the DAG. Enabling technology rather than the service identity. Broad comparison requiring exact live-signature review.
Neighborhood in Abstraction Space¶
Infrastructure as a service sits in a moderately populated region (48th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.
Family — Software & Systems Architecture (29 abstractions)
Nearest neighbors
- Software-defined data center — 0.91
- Cooperative storage cloud — 0.86
- Patch management — 0.86
- Autonomic Computing — 0.86
- Interface-Based Programming — 0.86
Computed from structural-signature embeddings · 2026-10-08