Cloud Cost Optimization

---
name: cost-optimization
description: "The skill guides engineers to reduce cloud spend without sacrificing performance by applying rightsizing, RI/Savings Plans, autoscaling, and cost governance."
metadata:
  tags: "cloud-cost-optimization, cloud-cost-management, devops, cost-visibility, rightsizing, autoscaling, cost-governance"
  source: "https://skilldb.dev/skills/devops-cloud-skills/cost-optimization"
  pack: "devops-cloud-skills"
  category: "Technology & Engineering"
---

# Cloud Cost Optimization

## When to use this skill
Use when the user says things like:
- "How can I optimize cloud costs?"
- "Help me reduce cloud spending without losing performance."
- "Analyze my cloud bill and suggest savings."
- "Provide cost governance and tagging guidance."
- "Recommend rightsizing and autoscaling strategies."


## Core Philosophy
Cloud cost optimization is the ongoing practice of aligning cloud spending with
actual business value. The cloud's pay-as-you-go model is a double-edged sword:
it eliminates upfront capital expenditure but can produce runaway costs without
discipline. Effective cost management treats cloud spending as an engineering
problem, not just a finance concern. Every engineer who provisions resources is
making spending decisions and should be empowered with visibility and accountability.

## Key Techniques
- **Rightsizing**: Analyze actual resource utilization and resize instances, databases,
  and storage to match real workload requirements. Most cloud resources are
  significantly over-provisioned.
- **Reserved Instances and Savings Plans**: Commit to steady-state usage for 1-3
  years in exchange for significant discounts (30-70%). Apply to predictable
  baseline workloads.
- **Spot/Preemptible Instances**: Use discounted interruptible compute (60-90% off)
  for fault-tolerant workloads like batch processing, CI/CD, and stateless workers.
- **Auto-Scaling**: Scale resources dynamically with demand rather than provisioning
  for peak capacity at all times.
- **Storage Tiering**: Move infrequently accessed data to cheaper storage classes
  (S3 Infrequent Access, Glacier, Archive) automatically using lifecycle policies.
- **Cost Allocation Tags**: Tag every resource with business metadata (team, project,
  environment) to attribute costs accurately and identify waste by owner.

## Best Practices
- Implement cost visibility dashboards accessible to engineering teams, not just
  finance.
- Set up billing alerts at multiple thresholds to catch unexpected spending spikes
  early.
- Review costs weekly and investigate any line item that increased more than 20%.
- Shut down non-production environments outside business hours. Development and
  staging resources running 24/7 can cost as much as production.
- Delete unused resources aggressively: unattached EBS volumes, old snapshots,
  idle load balancers, orphaned elastic IPs.
- Use cost as a metric in architecture reviews. A design that costs 3x more should
  deliver proportionally more value.
- Negotiate enterprise discount programs when total cloud spend justifies it.

## Common Patterns
- **FinOps Practice**: A cross-functional team of engineering, finance, and operations
  that continuously optimizes cloud spending through data-driven decisions.
- **Showback/Chargeback**: Attribute cloud costs to the teams that generate them,
  creating natural incentives for efficiency.
- **Spot Fleet with Fallback**: Run workloads on spot instances with automatic
  fallback to on-demand when spot capacity is unavailable.
- **Reserved Instance Portfolio**: Maintain a mix of 1-year and 3-year reservations
  across instance families to balance commitment risk with discount depth.

## Anti-Patterns
- Optimizing only at the infrastructure level while ignoring application efficiency.
  A poorly written query can cost more than an oversized instance.
- Buying reserved instances without understanding actual usage patterns. Unused
  reservations are wasted money.
- Treating all environments equally. Production needs redundancy and performance;
  development does not.
- Ignoring data transfer costs. Cross-region and internet egress charges can be
  surprisingly large.
- Over-optimizing to the point of fragility. Extreme cost cutting that eliminates
  redundancy or monitoring creates incident risk that costs more than the savings.
- Not accounting for the engineering time spent on optimization. If an engineer
  spends a week saving ten dollars per month, the ROI is negative.