SkarpChapter 2 of 20
Core Cloud Concepts and the Value of the AWS Cloud
Before touching a single AWS service, anchor your understanding in what cloud computing is, why organizations move to AWS, and how AWS transforms the way IT delivers value.
From On-Premises to Cloud: The Big Picture
Why Start With Concepts?
Before learning specific AWS services, you need a solid mental model of what cloud computing is and how it differs from traditional IT.
Traditional On-Premises IT
On-premises IT means your organization buys and runs its own servers, storage, and networking in its own data center or colocation space.
Cloud Computing in Contrast
Cloud computing lets you access computing resources over the internet on demand, paying only for what you use, while the provider runs the physical infrastructure.
Exam-Relevant Outcomes
For CLF-C02 you must compare on-prem vs cloud, explain AWS benefits, and understand deployment and service models at a conceptual level.
What Is Cloud Computing? Core Characteristics
Cloud Is More Than Hosting
Cloud computing has specific characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service.
On-Demand & Broad Access
On-demand self-service means you can provision resources yourself at any time. Broad network access means you use standard networks and protocols like HTTPS.
Resource Pooling
AWS pools huge amounts of hardware and serves many customers via multi-tenancy. You choose locations like Regions, not specific servers.
Elastic & Measured
Rapid elasticity lets you scale capacity up or down quickly. Measured service means your usage is tracked and billed pay-as-you-go.
Traditional On-Premises vs AWS Cloud
On-Prem: Heavy Up-Front Investment
On-premises IT requires buying hardware, waiting for delivery, installing equipment, and overprovisioning for peak load.
AWS: Provision in Minutes
In AWS, you launch EC2, S3, and RDS in minutes, start small, and scale only if demand grows, paying for what you use.
Cost and Speed
On-prem uses CapEx and is slow to change; AWS uses OpEx, enabling rapid experimentation and faster time to market.
Responsibility Shift
On-prem you manage everything; in AWS you share responsibilities with AWS, which runs the physical infrastructure.
AWS Cloud Value Proposition: Agility, Elasticity, and Global Reach
Agility: Move Fast
Agility means you can quickly create, modify, and shut down environments, enabling rapid experimentation and faster delivery.
Elasticity: Match Demand
Elasticity lets you scale resources up and down automatically based on demand, improving both performance and cost.
Global Reach: Serve Users Worldwide
AWS has a global infrastructure so you can deploy applications closer to users in different countries and regions.
Mapping to Scenarios
Needs like rapid launch, unpredictable traffic, or multi-country users usually point to agility, elasticity, and global reach.
AWS Global Infrastructure: Regions and Availability Zones
AWS Region: Key Definition
An AWS Region is a physical location in the world where we cluster data centers. Each Region is isolated from others.
Availability Zone: Key Definition
An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
Designing for Resilience
You spread resources across multiple AZs within a Region to survive data center failures and improve availability.
Common Exam Trap
Do not confuse Regions with AZs: Regions are geographic areas; AZs are distinct data centers inside a Region.
Cloud Deployment Models: Public, Private, Hybrid
Public Cloud
Public cloud means a provider like AWS owns and runs infrastructure, delivering services over the internet to many customers.
Private Cloud
Private cloud is dedicated infrastructure for a single organization, on-premises or hosted, but not shared with others.
Hybrid Cloud
Hybrid cloud connects on-prem or private environments with public cloud, so workloads can span both worlds.
Reading Exam Scenarios
Cloud bursting or mixing on-prem with AWS points to hybrid; dedicated single-tenant infrastructure points to private cloud.
Cloud Service Models: IaaS, PaaS, SaaS
The Responsibility Stack
Service models differ in how much of the stack you manage, from applications and data down to hardware and facilities.
IaaS: You Manage the OS
With IaaS like EC2, you manage the OS, runtime, data, and apps; AWS manages virtualization, hardware, and networking.
PaaS: Focus on Code and Data
With PaaS like Elastic Beanstalk or RDS, you manage applications and data; AWS manages OS, runtime, and infrastructure.
SaaS: Use the App
With SaaS, you just use the application via a browser or API while the provider manages almost everything behind the scenes.
Practical Scenarios: Mapping to Deployment and Service Models
Scenario 1: University Hybrid
Campus database on-prem plus EC2 exam servers in AWS over VPN: hybrid deployment, EC2 as IaaS.
Scenario 2: Startup on Beanstalk
Startup uploads code to Elastic Beanstalk in AWS public cloud: they use PaaS, focusing on code and data.
Scenario 3: Online Payroll
HR uses a browser-based payroll system: this is usually public cloud SaaS, a complete app delivered as a service.
Scenario 4: Bank Private Cloud
A bank’s internal virtualized environment with self-service VMs is a private cloud, often offering IaaS internally.
Thought Exercise: Design a Simple App on AWS
Imagine you are asked to design a basic notes application for students. It should:
- Be accessible from anywhere via a browser
- Handle exam-week traffic spikes
- Store notes reliably with backups
- Launch quickly with minimal up-front cost
Your tasks
- Choose a deployment model
Would you use public, private, or hybrid cloud for this app? Why? Write down your reasoning in 2–3 sentences.
- Choose a service model
Would you prefer IaaS, PaaS, or SaaS for the application backend? Consider:
- How much control you need over the OS and runtime
- How much operational work you want to avoid
- Pick example AWS services
Without worrying about deep details, pick at least:
- One compute service (for example, EC2, Elastic Beanstalk, AWS Lambda)
- One storage or database service (for example, S3, RDS, DynamoDB)
- Map to cloud characteristics
For each design choice, note which cloud characteristics it leverages:
- On-demand self-service
- Broad network access
- Resource pooling
- Rapid elasticity
- Measured service
Pause and actually write your design and reasoning. When you later review your answers with a mock exam or instructor, focus on whether your choices match the problem’s needs (cost, agility, elasticity, global reach).
Checkpoint Quiz: Core Concepts
Answer this question to check your understanding of cloud characteristics and models.
A company wants to experiment with a new analytics workload. They need to provision resources in minutes, scale them up and down based on usage, and pay only for what they consume. Which two essential characteristics of cloud computing are MOST relevant?
- Broad network access and resource pooling
- On-demand self-service and rapid elasticity
- Measured service and private cloud
- Hybrid deployment and SaaS
Show Answer
Answer: B) On-demand self-service and rapid elasticity
The scenario highlights quickly provisioning resources (on-demand self-service) and scaling up and down based on usage (rapid elasticity). Broad network access and resource pooling are also characteristics of cloud computing, but they are not the focus here. Measured service is about billing and monitoring, and private cloud, hybrid, and SaaS are not cloud characteristics; they are deployment and service models.
Checkpoint Quiz: Deployment and Service Models
Test your ability to classify deployment and service models.
Your organization uses an email service that runs entirely in a web browser. The provider manages all servers, storage, and software. How should you classify this solution?
- Public cloud SaaS
- Private cloud IaaS
- Hybrid cloud PaaS
- Public cloud IaaS
Show Answer
Answer: A) Public cloud SaaS
A browser-based email service managed entirely by the provider is Software as a Service (SaaS). Because it is delivered over the internet and shared across many customers, it is typically hosted in a public cloud. You are not managing VMs or OS, so it is not IaaS or PaaS.
Flashcards: Key Terms to Memorize
Use these flashcards to solidify core definitions. Say each answer out loud before flipping.
- AWS Region
- An AWS Region is a physical location in the world where we cluster data centers.
- Availability Zone (AZ)
- An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
- Infrastructure as a Service (IaaS)
- Cloud service model where you manage OS, runtime, data, and applications, while the provider manages virtualization, servers, storage, networking, and facilities. Example: Amazon EC2.
- Platform as a Service (PaaS)
- Cloud service model where you manage applications and data, while the provider manages runtime, OS, virtualization, hardware, and networking. Example: AWS Elastic Beanstalk.
- Software as a Service (SaaS)
- Cloud service model where the provider delivers a complete application over the internet, and you typically just configure and use it via a browser or API.
- On-demand self-service
- Ability for customers to provision computing resources automatically without requiring human interaction with each service provider.
- Rapid elasticity
- Ability to quickly scale resources up or down, often automatically, so capacity appears unlimited to the customer.
- Public cloud
- Cloud deployment model where a provider offers services over the internet using shared infrastructure for multiple customers, with logical isolation.
- Private cloud
- Cloud deployment model with infrastructure dedicated to a single organization, on-premises or hosted, not shared with others.
- Hybrid cloud
- Cloud deployment model that combines on-premises or private cloud resources with public cloud services, enabling workloads to span both.
Key Terms
- Agility
- The ability to quickly create, modify, and decommission IT resources, enabling rapid experimentation and faster delivery of new features.
- AWS Region
- An AWS Region is a physical location in the world where we cluster data centers.
- Elasticity
- The ability of a system to automatically scale resources up or down in response to changes in demand.
- Global reach
- The ability to deploy applications and store data in multiple geographic locations worldwide using a provider’s infrastructure.
- Hybrid cloud
- Deployment model that integrates on-premises or private cloud resources with public cloud services, allowing data and applications to move between them.
- Public cloud
- Deployment model where cloud services are delivered over the internet from shared infrastructure operated by a provider, serving multiple customers.
- Private cloud
- Deployment model where cloud infrastructure is dedicated to a single organization, providing cloud-like capabilities but not shared with others.
- Cloud computing
- A model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or provider interaction.
- Measured service
- Cloud characteristic where resource usage is automatically monitored, controlled, and reported, enabling pay-as-you-go billing.
- Resource pooling
- Cloud characteristic where the provider’s resources are pooled to serve multiple customers, with resources dynamically assigned and reassigned according to demand.
- Availability Zone
- An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
- Broad network access
- Cloud characteristic where services are available over the network and accessed through standard mechanisms, promoting use by heterogeneous client platforms.
- On-premises (on-prem)
- Traditional IT model where an organization owns, operates, and manages its own physical servers, storage, networking, and data center facilities.
- Platform as a Service (PaaS)
- Cloud service model that provides a platform allowing customers to develop, run, and manage applications without dealing with the underlying infrastructure.
- Software as a Service (SaaS)
- Cloud service model where a complete application is delivered over the internet, managed entirely by the provider and accessed by users via web or API.
- Infrastructure as a Service (IaaS)
- Cloud service model that provides fundamental computing resources such as virtual machines, storage, and networking, on top of which customers deploy and manage their own software.