5.2 The Optimize Phase

FinOps Certified Practitioner Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The Challenge of Cloud

1.1 The Paradigm Shift of Cloud Spend 1.2 Complexity and Scale of Cloud Waste 1.3 Introduction to FOCUS

2 Chapter 2: FinOps Overview & Core Principles

2.1 Defining FinOps and Its Business Value 2.2 The Six Core FinOps Principles 2.3 FinOps Maturity Model

3 Chapter 3: Personas, Teams, and Motivation

3.1 FinOps Personas and Their Incentives 3.2 Structuring the FinOps Team 3.3 Managing Culture and Incentives

4 Chapter 4: Core FinOps Capabilities

4.1 Cost Allocation & Metadata 4.2 Budgeting, Forecasting & Trend Analysis 4.3 Anomaly Management & Cost Avoidance 4.4 Rate Optimization & Commitments 4.5 Workload Optimization & Governance

5 Chapter 5: The FinOps Lifecycle Phases

5.1 The Inform Phase 5.2 The Optimize Phase 5.3 The Operate Phase 5.4 Transitioning and Aligning Across Phases 5.5 Establishing a FinOps Cadence

6 Chapter 6: Cloud Billing Anatomy & Terminology

6.1 Cloud Bill Anatomy and Pricing Models 6.2 Shared Cost Allocation Methodologies 6.3 Data Normalization and Multi-Cloud Complexity

5.2 The Optimize Phase

Key Takeaways Explain This Topic AI

The Optimize phase focuses on reducing cloud waste and improving unit economics.

Usage Optimization involves rightsizing resources and eliminating idle or unattached components.

Rate Optimization involves securing discounts through commitment-based models like Reserved Instances or Savings Plans.

Optimization is an ongoing process, not a one-time event, requiring collaboration between engineering and finance.

Last updated: July 2026

The Optimize Phase: Maximizing Cloud Value

Once an organization has established visibility in the Inform phase, it inevitably discovers inefficiencies. The Optimize phase is where action is taken to reduce waste, secure better pricing, and improve the overall unit economics of cloud consumption. It is important to emphasize that optimizing does not always mean "spending less in total." It means "getting the maximum business value for every dollar spent."

Cloud optimization is broadly categorized into two main levers: Usage Optimization (using less or using smarter) and Rate Optimization (paying less for what you use).

Usage Optimization: Using Less and Using Smarter

Usage optimization focuses on the physical footprint of your cloud infrastructure. It requires deep engineering involvement because it alters the architecture, configuration, or lifecycle of the resources running the business applications.

Rightsizing and Re-architecting

Rightsizing is the process of matching the cloud resource specifications (CPU, memory, network, storage IOPS) to the actual performance requirements of the workload. In the data center days, developers often over-provisioned resources "just in case" to ensure performance for peak loads, leading to massive waste. In the cloud, this habit is financially disastrous.

For example, an engineer might provision a compute instance with 16 vCPUs and 64GB of RAM for a web server. However, monitoring tools reveal that over a 30-day period, the CPU utilization never exceeded 15%, and memory usage peaked at 8GB. Rightsizing would involve downscaling this instance to a smaller family type (e.g., 4 vCPUs and 16GB of RAM), potentially saving 50-75% of the cost while maintaining adequate performance.

Beyond simple rightsizing, usage optimization can involve re-architecting: moving from legacy virtual machines to containerized microservices, or adopting serverless architectures (like AWS Lambda or Azure Functions) where you only pay for millisecond execution times rather than 24/7 idle servers.

Eliminating Waste

Usage optimization also heavily features finding and terminating completely unused resources:

Idle Instances: Compute resources running 24/7 in non-production environments. Implementing scheduling (e.g., turning off Dev servers on weekends) can save up to 70% of the cost for those instances.

Unattached Volumes: Storage volumes that were detached from compute instances but never deleted. They continue to accrue monthly gigabyte charges.

Obsolete Snapshots: Retaining daily backups for years when the corporate retention policy only requires 30 days.

Zombie IP Addresses and Load Balancers: Public IP addresses that are reserved but not attached, or load balancers with zero backend targets routing no traffic.

Rate Optimization: Paying Less

Rate optimization focuses on lowering the price paid per unit of cloud resource. It is typically driven by the FinOps, procurement, or central finance team and rarely requires engineering effort or architectural changes. The primary goal is to shift spend away from expensive "on-demand" pricing.

Commitment-Based Discounts and Purchasing Strategies

Reserved Instances (RIs): A commitment to use a specific type of resource (e.g., a specific database engine or compute family) in a specific region for a 1- or 3-year term. In exchange, the provider offers a significant discount (often up to 70%). RIs are less flexible but offer the highest predictability.

Savings Plans: A more flexible commitment model (popularized by AWS and adopted by others) where the organization commits to a specific dollar amount of spend per hour (e.g., $50/hour) for a 1- or 3-year term, regardless of the instance type, size, or region. This offers slightly lower discounts than standard RIs but significantly more flexibility as workloads evolve.

Spot Instances: Utilizing spare, unused cloud capacity at steep discounts (up to 90%). However, these instances can be interrupted and reclaimed by the provider with very short notice (often 2 minutes). Spot instances are ideal for fault-tolerant, stateless workloads like big data batch processing or containerized worker nodes.

Enterprise Discount Programs (EDP): Custom negotiated contracts where a company commits to a massive overall annual spend in exchange for a flat percentage discount across all services.

Rate vs. Usage Optimization Table

Feature Usage Optimization Rate Optimization

Primary Goal Reduce the amount of resources consumed. Reduce the price paid per resource unit.

Primary Actor Engineering / DevOps FinOps / Finance / Procurement

Examples Rightsizing, terminating idle resources, auto-scaling, serverless. Savings Plans, Reserved Instances, Spot Instances, Enterprise Discounts.

Risk Factor Potential performance impact if rightsized too aggressively. Financial lock-in if workloads migrate or shrink unexpectedly before the term ends.

Real-World Example: The Optimization Sequence

Consider "DataStream Corp." They identified high costs in their big data processing pipeline. First, they tackled Usage Optimization . The engineering team realized their worker nodes were idle 40% of the time. They implemented auto-scaling to spin down nodes when the queue was empty. They also rightsized their master node from a compute-optimized instance to a memory-optimized instance, better fitting the workload profile.

Second, they tackled Rate Optimization . Now that the usage was optimized and stable, the FinOps team analyzed the new baseline. They purchased a 1-year Compute Savings Plan to cover the 24/7 baseline load. For the variable, fault-tolerant worker nodes, they switched from on-demand to Spot Instances.

Through this combined approach, DataStream Corp reduced their pipeline costs by 62% without sacrificing processing speed. This highlights a crucial FinOps principle: Always optimize usage before optimizing rates. Purchasing a 3-year reservation for an oversized, wasteful instance simply locks in the waste, preventing future architectural efficiencies.