AWS Compute Purchasing Options: Curriculum Overview
Compute purchasing options (for example, On-Demand Instances, Reserved Instances, Spot Instances, AWS Savings Plans, Dedicated Hosts, Dedicated Instances, Capacity Reservations)
AWS Compute Purchasing Options: Curriculum Overview
This curriculum provides a comprehensive guide to understanding and comparing AWS pricing models for compute resources. Mastering these options is critical for the AWS Certified Cloud Practitioner (CLF-C02) exam and for real-world cost optimization in the cloud.
Prerequisites
Before starting this module, students should have a baseline understanding of the following:
- Cloud Economics Fundamentals: The difference between Capital Expenditure (CapEx) and Operational Expenditure (OpEx).
- Amazon EC2 Basics: Understanding what an instance is, what Amazon Machine Images (AMIs) are, and the basic concept of virtual computing.
- AWS Global Infrastructure: Familiarity with Regions and Availability Zones (AZs).
Module Breakdown
The curriculum is structured into five core modules, progressing from standard usage to specialized isolation and capacity requirements.
| Module | Focus Area | Key Concepts |
|---|---|---|
| Mod 1 | Flexible Consumption | On-Demand Instances, Per-second billing |
| Mod 2 | Commitment & Savings | Reserved Instances (RI), AWS Savings Plans |
| Mod 3 | Excess Capacity | Spot Instances, Fault-tolerance, 2-minute warnings |
| Mod 4 | Physical Isolation | Dedicated Hosts vs. Dedicated Instances |
| Mod 5 | Capacity Assurance | On-Demand Capacity Reservations |
Module Objectives
Module 1: Flexible Consumption
- Define On-Demand pricing and identify its use for unpredictable, short-term workloads.
- Explain why On-Demand is the most expensive but most flexible tier.
Module 2: Commitment & Savings
- Compare Reserved Instances (RI) and AWS Savings Plans.
- Understand the commitment levels (1-year or 3-year) and payment options (All Upfront, Partial Upfront, No Upfront).
- Describe the flexibility of Savings Plans across instance families and regions.
Module 3: Excess Capacity
- Identify use cases for Spot Instances (e.g., batch processing, background tasks).
- Explain the mechanics of the Spot market and how AWS reclaims capacity.
Module 4: Isolation & Compliance
- Differentiate between Dedicated Instances (hardware isolation at the VPC level) and Dedicated Hosts (physical server visibility and licensing).
Module 5: Capacity Assurance
- Explain the purpose of Capacity Reservations in ensuring instances can be launched in a specific AZ regardless of demand.
Visual Anchors
Compute Options Mind Map
Cost vs. Commitment Trade-off
Success Metrics
To demonstrate mastery of this curriculum, the student must be able to:
- Select the correct model for a scenario: (e.g., "Which model is best for a steady-state database running 24/7?" -> Savings Plan/RI).
- Calculate Savings: Understand that "All Upfront" payments provide the deepest discounts compared to "No Upfront."
- Differentiate Isolation: Explain that Dedicated Hosts allow for "Bring Your Own License" (BYOL) while Dedicated Instances do not.
- Manage Interruption: Identify that Spot Instances provide a 2-minute notification before termination.
Real-World Application
- FinOps & Cloud Financial Management: Professionals use these models to reduce a company's "Cloud Waste." Efficient use of Spot and Savings Plans can reduce monthly AWS bills by 40-70%.
- Architecting for High Availability: Using On-Demand Capacity Reservations for critical disaster recovery (DR) events ensures that capacity is available when a secondary region needs to spin up immediately.
- Compliance: Industries like Banking or Healthcare use Dedicated Hosts to meet regulatory requirements for physical server isolation.
Examples & Scenarios
[!TIP] Always match the purchasing option to the workload's tolerance for interruption and its duration.
| Scenario | Recommended Option | Why? |
|---|---|---|
| Development & Testing | On-Demand | Low commitment; instances are turned off when not in use. |
| Steady-State Production Web Server | Savings Plan | Constant usage over 1-3 years; maximum savings for predictable load. |
| Large-scale Data Analysis (Batch) | Spot Instances | If the job can be restarted, the 90% discount outweighs the risk of interruption. |
| Legacy Software requiring specific HW IDs | Dedicated Host | Provides visibility into the physical socket/core for licensing compliance. |
| Black Friday Traffic Spike | On-Demand Capacity Reservation | Ensures that when the spike hits, the capacity is guaranteed to be available in that AZ. |
▶Deep Dive: Spot Instance Interruption Behavior
When AWS needs the capacity back for On-Demand users, Spot instances receive a termination notice. Your application should be designed to save its state to S3 or a database within that 2-minute window to avoid data loss.