finops-patternslisted

# FinOps Patterns Best practices for managing cloud financial operations -- visibility, optimization, and governance of cloud spend at scale. ## Cloud Cost Anatomy Understanding where cloud money goes is the first step to controlling it. ``` Total Cloud Spend | +-- Compute (60-70%) | +-- VMs / Instances | +-- Containers (EKS, GKE, ECS) | +-- Serverless (Lambda, Cloud Functions) | +-- GPU / ML Training | +-- Storage (15-20%) | +-- Block (EBS, Persistent Disks) | +-- Object (S3, GCS, Blob) | +-- Database (RDS, Cloud SQL, DynamoDB) | +-- Network (10-15%) | +-- Data Transfer (egress is expensive) | +-- Load Balancers | +-- CDN | +-- VPN / Direct Connect | +-- Other (5-10%) +-- Monitoring / Logging +-- DNS / Certificates +-- Support Plans +-- Marketplace ``` | Cost Driver | Typical Waste | Quick Win | |------------|--------------|-----------| | Idle instances | 20-30% of compute | Schedule dev/test shutdown nights + weekends | | Over-provisioned instances | 40-60% of instances | Rightsize based on actual CPU/memory usage | | Unattached storage volumes | 5-10% of storage | Automated cleanup of orphaned EBS/disks | | Unused Elastic IPs | Small but cumulative | Release unattached IPs | | Old snapshots | 10-20% of storage | Lifecycle policy with retention limits | | Cross-region data transfer | 5-15% of network | Co-locate services in same region | ## FinOps Maturity