AWS Purchasing Options: Cost Optimization Strategy Guide

This guide covers the core purchasing models available in AWS, essential for the SAP-C02 exam. Understanding how to balance cost, flexibility, and commitment is the key to mastering cost optimization.

Learning Objectives

By the end of this guide, you should be able to:

• Differentiate between On-Demand, Reserved Instances, Savings Plans, and Spot Instances.
• Recommend the most cost-effective model based on specific workload patterns (steady-state, spiky, or flexible).
• Identify the specific benefits and limitations of Compute Savings Plans versus EC2 Instance Savings Plans.
• Design architectures that gracefully handle Spot Instance interruptions.

Key Terms & Glossary

• On-Demand Instances: Pay-as-you-go pricing without long-term commitments; highest price point but maximum flexibility.
• Reserved Instances (RI): A commitment to use a specific instance configuration for 1 or 3 years in exchange for a discount.
• Savings Plans (SP): A flexible pricing model that offers low prices in exchange for a commitment to a consistent amount of usage (measured in $/hour).
• Spot Instances: Spare compute capacity offered at up to 90% discount, subject to reclamation by AWS.
• Standard RI: The least flexible RI; cannot change instance families.
• Convertible RI: An RI that allows changing instance families, though typically offers a lower discount than Standard RIs.

The "Big Idea"

AWS cost optimization is not just about choosing the cheapest option; it is about mapping the right financial model to the application's availability requirements. Steady-state workloads belong on committed models (RI/SP), while flexible, fault-tolerant workloads belong on Spot. On-Demand is merely the "buffer" for unpredictable spikes.

Formula / Concept Box

Hierarchical Outline

• 1. Committed Use Models
  • Reserved Instances (RI)
    • Standard vs. Convertible: Flexibility vs. depth of discount.
    • Regional vs. Zonal: Regional provides capacity reservation; Zonal provides specific AZ placement.
  • Savings Plans (SP)
    • Compute Savings Plans: Applies to EC2, Fargate, and Lambda across any region/family.
    • EC2 Instance Savings Plans: Restricted to a specific instance family in a region but offers deeper discounts.
• 2. Opportunity-Based Models
  • Spot Instances
    • Capacity Pools: Pricing varies by AZ and Instance Type.
    • Termination Notices: 2-minute warning via CloudWatch Events or Instance Metadata.
• 3. Payment Options
  • All Upfront: Largest discount.
  • Partial Upfront: Balanced approach.
  • No Upfront: Monthly billing, lowest discount level.

Visual Anchors

Decision Flow: Choosing a Purchasing Option

The Cost vs. Flexibility Trade-off

\begin{tikzpicture}[scale=0.8] \draw[->, thick] (0,0) -- (8,0) node[right] {Flexibility}; \draw[->, thick] (0,0) -- (0,6) node[above] {Cost Savings};

\end{tikzpicture}

Definition-Example Pairs

• Compute Savings Plans
  • Definition: A commitment to a $/hr spend that applies to EC2 regardless of instance family, size, region, OS, or tenancy, and extends to Fargate and Lambda.
  • Example: A company migrates their web tier from EC2 m5.large in us-east-1 to Fargate in us-west-2; the Compute Savings Plan discount follows them automatically.
• Spot Instance Reclaiming
  • Definition: AWS taking back capacity when on-demand demand increases, providing a 2-minute notice.
  • Example: A video transcoding farm processes individual frames; when an instance is reclaimed, the job is saved and picked up by another instance later, saving 85% in total costs.

Worked Examples

Scenario: The m5.large Comparative Analysis

Based on the source data for Stockholm (m5.large), let's compare the 3-year commitment options for a single instance:

1. Standard Reserved Instance (Full Upfront): Costs approximately $1,008 for 3 years.
2. EC2 Instance Savings Plan (Full Upfront): Costs approximately $998.64 for 3 years.
3. Compute Savings Plan (Full Upfront): Costs approximately $1,392.84 for 3 years.

Analysis: If you know for certain you will stay on the m5 family in Stockholm, the EC2 Instance Savings Plan is the cheapest committed option. However, if you plan to move to m6g (Graviton) or migrate to Lambda, the Compute Savings Plan is the only one that provides a discount, despite its higher absolute price than the specific EC2 plan.

Checkpoint Questions

1. Which purchasing model allows you to apply discounts to both AWS Lambda and Amazon EC2?
2. How much time do you have to gracefully shut down a Spot Instance once AWS issues a termination notice?
3. True or False: Standard Reserved Instances allow you to switch from C5 instances to M5 instances halfway through the term.
4. What is the primary difference between "No Upfront" and "All Upfront" payments regarding the total effective discount?

Muddy Points & Cross-Refs

• RI vs. Savings Plans: RIs are older and more rigid. Savings Plans are the modern recommendation for most users because they handle "size-flexibility" automatically without the need for manual modifications.
• Spot Capacity Pools: Remember that Spot price is not one single price. It varies by AZ. If us-east-1a is expensive for m5.large, us-east-1b might be 40% cheaper.
• Regional vs. Zonal RI: This is a common exam trap. Regional RIs provide a discount but NO capacity reservation. Zonal RIs provide a capacity reservation in a specific AZ but are less flexible for discounting other instances in the region.

Comparison Tables

Feature Comparison: RIs vs. Savings Plans

[!TIP] For the SAP-C02 exam, always look for the "least administrative effort" solution. Savings Plans almost always beat Reserved Instances in this category.