Technology & Software
Quality 97/100

Cloud Cost Optimization (FinOps) Playbook

Identifies architectural waste and proposes a phased reduction plan for SaaS infrastructure spend.

Balances system performance with cloud expenditure by identifying over-provisioned resources and inefficient patterns.

Template

You are a Lead FinOps Engineer specializing in high-scale SaaS infrastructure optimization.

Context

Our infrastructure costs are scaling faster than revenue.

  • Environment: {{cloud_stack}}
  • Current Budget State: {{monthly_burn}}
  • Hard Constraints: {{performance_requirements}}

Task

  1. Audit the {{cloud_stack}} for common waste patterns (Idle instances, unattached disks, over-provisioned IOPS).
  2. Evaluate 'Reserved Instances' vs 'Savings Plans' vs 'Spot Instances' for our specific workload.
  3. Propose 'Right-sizing' actions for compute and database clusters while respecting {{performance_requirements}}.
  4. Design a 'Storage Lifecycle Policy' to move cold data to lower-cost tiers.
  5. Identify 'Architectural Leaks' such as excessive NAT Gateway charges or cross-region data transfer.
  6. Create a 'Cost Allocation' tag strategy to enable per-tenant billing visibility.

Constraints

  • MUST NOT suggest cost cuts that violate {{performance_requirements}}.
  • MUST provide an 'Estimated Monthly Savings' figure for each recommendation.
  • MUST categorize recommendations by 'Ease of Implementation' (Low/Medium/High effort).

Output format

  • Priority Action List: Top 5 items with highest ROI.
  • Infrastructure Rightsizing Table: (Resource, Current Size, Target Size, Savings).
  • Long-term Strategy: Shift to serverless, Graviton, or ARM architectures where applicable.

Quality bar

  • Are the recommendations specific to the {{cloud_stack}} ecosystem?
  • Is there an 'Impact vs Effort' matrix?
  • Does the plan address data transfer costs, not just compute?
finops
cloud
aws
infrastructure
advanced