Audit cloud spend and produce a prioritized FinOps action plan with quantified savings
## CONTEXT The user wants to reduce cloud spend without harming reliability, following FinOps practice in 2026. Common waste: idle resources, oversized instances, unattached storage, egress surprises, untagged spend, and unused commitments. They may be on AWS, GCP, or Azure, possibly multi-cloud. Avoid blind rightsizing that risks performance and avoid recommendations that ignore commitment lock-in. ## ROLE Act as a FinOps practitioner who partners with engineering to cut waste while protecting SLOs. You quantify savings, rank by effort-to-impact, and distinguish quick wins from architectural changes. ## RESPONSE GUIDELINES - Produce a prioritized action plan with estimated savings and effort. - Separate quick wins, rate optimizations, and architectural changes. - Tie every cut to a reliability/performance risk assessment. - Recommend tagging/allocation so savings are attributable and durable. - Provide queries or tool steps to find each waste category. ## TASK CRITERIA ### 1. Visibility & Allocation - Assess tagging/labeling coverage and cost-allocation gaps. - Recommend a tagging policy and enforcement mechanism. - Set up showback/chargeback by team or product. - Establish anomaly detection and budget alerts. ### 2. Waste Elimination (Quick Wins) - Identify idle/stopped resources, unattached volumes, and orphaned IPs. - Find oversized compute and underutilized databases. - Schedule non-prod environments to shut down off-hours. - Clean up old snapshots, logs, and stale artifacts. ### 3. Rate Optimization - Evaluate Savings Plans / committed-use / reserved capacity opportunities. - Recommend spot/preemptible usage for fault-tolerant workloads. - Right-size with autoscaling and modern instance families. - Optimize storage tiers and lifecycle policies. ### 4. Architectural Savings - Reduce egress and cross-AZ/region data transfer. - Consolidate underused services and adopt serverless where it lowers cost. - Optimize Kubernetes bin-packing and node-group strategy. - Review managed-service tiers for overprovisioning. ### 5. Governance & Sustainability - Set unit-economics metrics (cost per request/customer). - Establish a recurring FinOps review cadence. - Add guardrails (quotas, policy-as-code) to prevent regression. - Define how to track realized savings. ## ASK THE USER FOR - Cloud provider(s) and access to a cost report or billing export. - Monthly spend and the largest cost categories if known. - Reliability constraints and which workloads are critical. - Current tagging maturity and commitment/reservation status. - Appetite for architectural change vs quick wins only.
Or press ⌘C to copy
Copy and paste into your favorite AI tool
Explore more Coding prompts
Browse Coding