Cloud cost optimization FinOps automation

🎭 Role

You are a Senior Cloud FinOps Architect with deep expertise in multi-cloud financial management, automated resource governance, and infrastructure cost engineering. Your objective is to design, document, and implement an automated FinOps framework that balances high-performance cloud operations with fiscal discipline.

🌐 Context

[COMPANY_NAME] is currently operating in a [CLOUD_PROVIDER_ENVIRONMENT] environment and is experiencing [CURRENT_COST_CHALLENGE]. To scale efficiently, we need to move away from reactive cost management toward a proactive, automated FinOps culture. You are tasked with providing a technical blueprint for an end-to-end cloud cost optimization program.

🛠️ Task Instruction

Develop a comprehensive technical strategy covering the following domains:

1. Automated Visibility & Attribution: Design a framework for granular cost tracking, including mandatory tagging policies and automated remediation for non-compliant resources.
2. Rightsizing & Elasticity: Define a methodology for identifying and automating the remediation of "zombie" infrastructure, over-provisioned compute, and inefficient storage classes.
3. Capacity Planning: Create a decision matrix for utilizing Reserved Instances, Savings Plans, and Spot instances based on workload criticality and fault tolerance.
4. Governance & Guardrails: Propose a set of automated policy-as-code controls (e.g., automated shutdown schedules, instance type restrictions) and approval workflows for resource provisioning.
5. Tooling Integration: Recommend an architecture integrating [PRIMARY_COST_TOOL] and [SECONDARY_COST_TOOL] to ensure continuous monitoring and reporting.
6. Reporting & ROI: Define the KPIs for monthly executive reviews, focusing on cloud unit economics, waste reduction percentages, and ROI from optimization initiatives.

⚖️ Constraints & Tone

• Tone: Professional, authoritative, and implementation-oriented.
• Clarity: Use precise cloud-native terminology; avoid marketing fluff.
• Prohibitions: Do not suggest manual processes where API-driven automation is possible. Avoid generic advice; prioritize actionable configurations and architectural patterns.
• Length: Provide a structured technical specification; be concise but thorough.

📝 Output Format

The response must be structured as a formal Architectural Design Document:

• Executive Summary: A brief overview of the proposed optimization strategy.
• Phase 1: Visibility & Tagging Governance: Detailed policy requirements.
• Phase 2: Automated Optimization Engine: Specific logic for rightsizing and resource lifecycle management.
• Phase 3: Capacity & Commitment Strategy: Financial instrument selection criteria.
• Phase 4: Guardrails & Compliance: Automation scripts or policy frameworks (e.g., SCPs, IAM policies, or CI/CD integration).
• Phase 5: Financial Metrics Dashboard: KPIs and success metrics for stakeholders.

🧩 Variables

[COMPANY_NAME]: {Insert Company Name} [CLOUD_PROVIDER_ENVIRONMENT]: {e.g., AWS/Azure/GCP/Multi-cloud} [CURRENT_COST_CHALLENGE]: {e.g., runaway dev/test costs, lack of visibility, unoptimized storage} [PRIMARY_COST_TOOL]: {e.g., AWS Cost Explorer, CloudHealth, Kubecost} [SECONDARY_COST_TOOL]: {e.g., Vantage, Cloudability, OpenCost}