Cloud Cost Optimization Architect

You are a FinOps practitioner and cloud architect. Help me optimize our cloud costs.

Cloud provider: [CLOUD_PROVIDER]
Current monthly spend: [MONTHLY_SPEND]
Spend breakdown: [SPEND_BREAKDOWN]
Architecture overview: [ARCHITECTURE]
Growth trajectory: [GROWTH]
Cost reduction target: [TARGET]

Optimize using FinOps principles:

**1. Cost Visibility**
- Tagging strategy for cost allocation (team, service, environment, feature)
- Cost anomaly detection setup
- Showback/chargeback model recommendation

**2. Right-sizing Analysis**
- Compute: Are instances over-provisioned? (check CPU/memory utilization)
- Database: Is the instance class too large?
- Storage: Are you paying for performance you don't need?
- Network: Egress optimization opportunities

**3. Pricing Model Optimization**
- Reserved Instances / Savings Plans analysis
  - Which workloads are stable enough for commitments?
  - 1-year vs. 3-year, partial vs. full upfront
  - Estimated savings (typically 30-60%)
- Spot/Preemptible instances for fault-tolerant workloads
- Free tier and credits usage

**4. Architecture Optimizations**
- Serverless opportunities (when Lambda/Cloud Functions beat always-on)
- Auto-scaling configuration (scale to zero when possible)
- Multi-region cost analysis (do you need all those regions?)
- CDN and edge caching to reduce origin costs
- Data transfer optimization (VPC endpoints, same-AZ placement)

**5. Storage Optimization**
- Lifecycle policies (hot → warm → cold → archive)
- Compression and deduplication
- Delete unused snapshots, AMIs, volumes
- S3 storage class analysis (Standard vs. IA vs. Glacier)

**6. Development & Testing Costs**
- Environment scheduling (shut down dev/staging overnight and weekends)
- Sandbox policies and budget limits
- Ephemeral environments over persistent ones

**7. Quick Wins** (implement this week):
| Action | Estimated Monthly Savings | Effort |

**8. Cost Optimization Roadmap**
- Month 1: Quick wins and visibility
- Month 2-3: Right-sizing and commitments
- Month 4-6: Architecture changes

**9. Governance**
- Budget alerts and thresholds
- Approval process for new resources
- Regular cost review cadence
- Unit economics tracking (cost per user, cost per transaction)