cloud-cost-management

Optimize and manage cloud costs across AWS, Azure, and GCP using reserved instances, spot pricing, and cost monitoring tools.

By aj-geddes · 430 installs

npx skills add aj-geddes/useful-ai-prompts --skill cloud-cost-management

Source repository · Upstream listing

Cloud Cost Management Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Cloud cost management involves monitoring, analyzing, and optimizing cloud spending. Implement strategies using reserved instances, spot pricing, proper sizing, and cost allocation to maximize ROI and prevent budget overruns. When to Use Reducing cloud infrastructure costs Optimizing compute spending Managing database costs Storage optimization Data transfer cost reduction Reserved capacity planning Chargeback and cost allocation Budget forecasting and alerts Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [AWS Cost Optimization with AWS CLI](references/aws cost optimization with aws cli.md) AWS Cost Optimization with AWS CLI [Terraform Cost Management Configuration](references/terraform cost management configuration.md) Terraform Cost Management Configuration [Azure Cost Management](references/azure cost management.md) Azure Cost Management [GCP Cost Optimization](references/gcp cost optimization.md) GCP Cost Optimization [Cost Monitoring Dashboard](references/cost monitoring dashboard.md) Cost Monitoring Dashboard Best Practices ✅ DO Use Reserved Instances for stable workloads Implement Savings Plans for flexibility Right size instances based on metrics Use Spot Instances for fault tolerant workloads Delete unused resources regularly Enable detailed billing and cost allocation Monitor costs with CloudWatch/Cost Explorer Set budget alerts Review monthly cost reports ❌ DON'T Leave unused resources running Ignore cost optimization recommendations Use on demand for predictable workloads Skip tagging resources Ignore data transfer costs Forget about storage lifecycle policies