How do you control cloud costs as part of DevOps (FinOps)?

Summary

Make cost visible and owned: consistent tagging and allocation per team and service, dashboards and budgets with alerts, cost reviewed alongside performance in design and pull requests where relevant; then optimise: right-size, autoscale, turn off idle non-production resources, use commitments (Savings Plans, reserved instances) for steady load and spot for interruptible work, and clean up orphaned resources.

Longer Answer

Common big wins: idle or oversized databases and instances, unattached volumes and old snapshots, NAT gateway and cross-zone data transfer, log and metric ingestion, and over-provisioned Kubernetes requests. FinOps is a collaboration between engineering, finance and product: engineers make the trade-offs, finance provides visibility and forecasting. Automate guardrails (policies requiring tags, budgets per account) rather than relying on monthly surprises.

Key Points

• Tagging, allocation, budgets, alerts.
• Right-size, autoscale, schedule non-prod.
• Commitments and spot.
• Data transfer and observability are hidden costs.