1.5 Cloud Economics
Key Takeaways
- Total Cost of Ownership (TCO) includes hidden on-premises costs — power, cooling, staffing, disaster recovery, and overprovisioning — not just hardware.
- Cloud computing converts Capital Expenditure (CapEx) into Operating Expenditure (OpEx), enabling pay-as-you-go pricing and better cash flow.
- Right-sizing means selecting the lowest-cost resource that still meets technical requirements — a continuous optimization process aided by AWS Compute Optimizer.
- Economies of scale let AWS lower per-unit costs as it grows, passing savings to customers through frequent price reductions.
- Use the Pricing Calculator to estimate before deployment, Cost Explorer to analyze after, and Budgets to receive spending alerts.
Understanding the financial benefits of cloud computing is a significant part of Domain 1. The CLF-C02 tests your ability to explain how cloud economics works and why organizations benefit financially from migrating to AWS.
Total Cost of Ownership (TCO)
Total Cost of Ownership (TCO) is the full cost of owning and operating IT infrastructure, including both direct and indirect costs. When comparing on-premises to cloud, organizations must account for ALL costs — not just the hardware sticker price.
On-Premises TCO Components
| Cost Category | Examples |
|---|---|
| Hardware | Servers, storage, networking equipment |
| Software | Licenses (OS, database, middleware) |
| Facilities | Data-center space, power, cooling, physical security |
| Personnel | Staff for maintenance, administration, troubleshooting |
| Network | Internet connectivity, WAN links |
| Disaster Recovery | Backup site, replication, DR testing |
| Overprovisioning | Extra capacity bought for peak demand, often idle |
Cloud TCO Components
| Cost Category | Examples |
|---|---|
| Compute | EC2 instances, Lambda invocations |
| Storage | S3, EBS, Glacier |
| Data Transfer | Outbound data-transfer charges |
| Managed Services | RDS, DynamoDB, and others |
On the Exam: TCO questions often highlight hidden on-premises costs people forget — power, cooling, staffing, overprovisioning, and disaster recovery. These costs shrink dramatically or disappear in the cloud.
Capital Expenditure vs. Operating Expenditure
| CapEx (Capital Expenditure) | OpEx (Operating Expenditure) | |
|---|---|---|
| Definition | Upfront investment in physical assets | Ongoing cost of running operations |
| Examples | Buying servers, building a data center | Monthly AWS bill, electricity, salaries |
| Accounting | Depreciated over time (3–5 years) | Expensed in the period incurred |
| Risk | Over- or under-provisioning | Pay only for what you use |
| Model | Traditional IT | Cloud computing |
Key benefit: Cloud computing converts CapEx to OpEx. This matters because it means no large upfront costs (start small and scale), better cash flow (pay monthly), reduced risk (no need to predict capacity years ahead), and potential tax advantages (OpEx is expensed in the year incurred).
Right-Sizing
Right-sizing is matching instance types and sizes to your actual workload performance and capacity needs at the lowest possible cost. It is a continuous process, not a one-time event, because workloads change over time.
Right-sizing strategies:
- Start small — begin with smaller instances and scale up only if needed
- Monitor utilization — use CloudWatch to track CPU, memory, and network usage
- Use recommendations — AWS Compute Optimizer analyzes usage and suggests optimal sizes
- Schedule scaling — turn off non-production instances outside business hours
- Choose the right instance family — compute-optimized vs. memory-optimized vs. general-purpose
Economies of Scale
As AWS adds more customers, its cost per unit of computing falls thanks to economies of scale, and AWS passes those savings to customers through regular price reductions. Since launch, AWS has reduced prices many dozens of times across its services. This is one of the six advantages of cloud: aggregated demand drives lower pay-as-you-go prices than any single organization could achieve alone.
AWS Cost Estimation and Management Tools
| Tool | Purpose |
|---|---|
| AWS Pricing Calculator | Estimate monthly costs for AWS services before you use them — ideal for TCO comparisons |
| AWS Cost Explorer | Visualize and analyze your current spending patterns over time |
| AWS Budgets | Set spending or usage thresholds and receive alerts |
| AWS Cost and Usage Report (CUR) | The most detailed cost and usage data available |
| AWS Trusted Advisor | Recommendations for cost savings (and other categories) |
On the Exam: Use the Pricing Calculator to estimate costs before deployment; use Cost Explorer to analyze costs after you are running; use Budgets to get alerts when spending crosses a threshold.
Licensing Considerations
When migrating to AWS, licensing models change:
- BYOL (Bring Your Own License): apply existing licenses on AWS (e.g., Windows Server, SQL Server)
- License Included: AWS bundles the license cost into the service price (e.g., Amazon RDS for SQL Server)
- Open Source: use free alternatives (e.g., PostgreSQL or MySQL on RDS instead of a commercial engine)
Together, TCO analysis, the CapEx-to-OpEx shift, right-sizing, and economies of scale explain why migrating to AWS often lowers total cost while improving agility — a recurring theme across both Domain 1 and Domain 4.
Consumption-Based Pricing and the Free Tier
Two ideas tie cloud economics together for the exam. First, consumption-based (pay-as-you-go) pricing means you are billed for actual usage — compute-seconds, gigabytes stored, requests served — with no upfront commitment, which is what makes the CapEx-to-OpEx shift possible. Second, the AWS Free Tier lets you try many services at no cost within limits (always-free offers, 12-months-free offers, and short-term trials), so teams can prototype before spending.
Combined with right-sizing and commitment-based discounts (Reserved Instances and Savings Plans), these mechanisms let an organization start small, pay only for what it uses, and lower unit costs as it grows.
Reserved Instances and Savings Plans in Brief
Commitment-based pricing is where the largest savings come from, so the exam expects you to recognize the two main vehicles. Reserved Instances (RIs) offer up to roughly 72% off On-Demand in exchange for a 1- or 3-year commitment to a specific instance configuration, ideal for steady-state workloads. Savings Plans offer comparable discounts for a 1- or 3-year commitment to a consistent amount of compute usage (measured in dollars per hour) with flexibility across instance families and, for Compute Savings Plans, across EC2, Fargate, and Lambda.
For unpredictable, fault-tolerant work, Spot Instances offer up to ~90% off using spare capacity AWS can reclaim. Matching workloads to the right pricing model is the core cost-optimization skill.
When comparing on-premises costs to cloud costs, which of the following is a commonly overlooked on-premises cost?
Which statement best describes the financial benefit of converting CapEx to OpEx through cloud computing?
What is 'right-sizing' in the context of AWS?
Which AWS tool helps estimate the cost of running a workload on AWS BEFORE you deploy it, for comparison against on-premises costs?
A company eliminates $500,000 per year in data-center power, cooling, and physical security by migrating to AWS. What does this represent?