Welcome to CloudSave Academy — you've just made one of the smartest investments in your cloud career.

What You'll Achieve

By the end of this course, you'll have the skills to cut your organization's cloud bill by 30-60% without sacrificing performance or reliability.

How This Course Works

📚 6 Chapters, 21 Lessons — structured from foundations to advanced automation

🔒 Sequential Progression — each lesson builds on the previous one

🎓 Certificate of Completion — prove your expertise to your team and employer

💬 Community Chat — ask questions, share wins, and connect with fellow optimizers

Recommended Learning Path

1. Start with Chapter 1 even if you're experienced — the tagging and FinOps frameworks are the foundation everything else depends on

2. Take notes on your own infrastructure as you go — apply each technique to your real environment immediately

3. Share your wins in the community — when you find $10K/month in waste (and you will), tell us about it

4. Complete the final capstone in Chapter 6 to build a custom optimization roadmap for your organization

Quick Wins to Look For

Most students find their first savings within the first week:

• Orphaned EBS volumes and snapshots (Chapter 2)

• Oversized instances running at 5-15% CPU (Chapter 3)

• Dev/test environments running 24/7 that should be scheduled (Chapter 6)

Let's get to work. Your cloud bill isn't going to optimize itself.

— CloudSave Academy

After helping teams optimize millions in cloud spend, here are the 5 techniques that consistently deliver the highest return for the least effort — ranked from easiest to hardest.

---

1. 🗓️ Schedule Dev/Test Environments (Savings: 65%+ | Effort: Low)

Most organizations run dev, staging, and QA environments 24/7. Your developers work ~10 hours/day, 5 days/week. That's 50 out of 168 hours — meaning 70% of those compute hours are pure waste.

Quick implementation:

# AWS CLI — stop instances tagged Environment=dev at 7pm
aws ec2 stop-instances --instance-ids $(aws ec2 describe-instances \
  --filters "Name=tag:Environment,Values=dev" "Name=instance-state-name,Values=running" \
  --query 'Reservations[].Instances[].InstanceId' --output text)

Use AWS Instance Scheduler, Azure Start/Stop VMs, or a simple cron + Lambda. Most teams save $2,000-$15,000/month on this alone.

---

2. 🧹 Kill Orphaned Resources (Savings: 5-15% of total bill | Effort: Low)

Every cloud account accumulates waste: unattached EBS volumes, old snapshots, idle load balancers, unused Elastic IPs, abandoned RDS instances.

Checklist to run right now:

• Unattached EBS volumes → aws ec2 describe-volumes --filters "Name=status,Values=available"

• Snapshots older than 90 days with no AMI dependency

• Elastic IPs not associated with running instances

• Load balancers with zero healthy targets

• Idle RDS instances (0 connections for 14+ days)

I've seen teams find $5K-$50K/month in orphaned resources on the first sweep.

---

3. 📐 Rightsize Compute Instances (Savings: 30-50% | Effort: Medium)

The average cloud instance runs at 15% CPU utilization. That means most instances are 3-5x larger than they need to be.

How to do it:

1. Pull 14 days of CPU + memory metrics from CloudWatch / Azure Monitor / Cloud Monitoring

2. Use AWS Compute Optimizer, Azure Advisor, or GCP Recommender for automated suggestions

3. Target instances consistently below 30% CPU — they're candidates for downsizing

4. Test one size down, validate for a week, then move to the next batch

Pro tip: Don't just downsize — check if a different instance family is better. A memory-optimized r6g.large might outperform a general m5.xlarge at half the cost for your workload.

---

4. 💰 Commit to Reserved Instances / Savings Plans (Savings: 30-72% | Effort: Medium)

If you have stable baseline workloads (and most production environments do), you're leaving money on the table by paying on-demand rates.

Decision framework:

• Savings Plans (AWS) → Best flexibility, covers EC2 + Fargate + Lambda

• Reserved Instances → Higher discount for specific instance types you won't change

• GCP CUDs → Spend-based for flexibility, resource-based for maximum discount

• Azure Reservations → 1-year or 3-year, can be exchanged if needs change

Golden rule: Only commit on workloads that have been stable for 3+ months. Start with 1-year terms. Never commit more than 80% of your baseline.

---

5. 🏗️ Migrate gp2 → gp3 EBS Volumes (Savings: 20% | Effort: Low)

This is free money. AWS gp3 volumes are 20% cheaper than gp2 with better baseline performance (3,000 IOPS vs 100 IOPS/GB). There is almost no reason to stay on gp2.

# Find all gp2 volumes
aws ec2 describe-volumes --filters "Name=volume-type,Values=gp2" \
  --query 'Volumes[].[VolumeId,Size,State]' --output table

# Modify to gp3 (online, no downtime)
aws ec2 modify-volume --volume-id vol-xxxxx --volume-type gp3

Migration is online — zero downtime. A team with 100 gp2 volumes typically saves $500-$2,000/month instantly.

---

The Compound Effect

These 5 optimizations alone can reduce your cloud bill by 30-50%. The key is to do them systematically, not as a one-time cleanup.

Build a monthly review cadence, assign ownership, and track savings over time. Cloud cost optimization isn't a project — it's a practice.

---

Want the full playbook? CloudSave Academy covers these techniques and 16 more across 6 chapters — from billing analysis to automated governance. Every lesson includes provider-specific implementations for AWS, Azure, and GCP.

After helping teams optimize millions in cloud spend, here are the 5 techniques that consistently deliver the highest return for the least effort — ranked from easiest to hardest.

---

1. 🗓️ Schedule Dev/Test Environments (Savings: 65%+ | Effort: Low)

Most organizations run dev, staging, and QA environments 24/7. Your developers work ~10 hours/day, 5 days/week. That's 50 out of 168 hours — meaning 70% of those compute hours are pure waste.

Quick implementation:

# AWS CLI — stop instances tagged Environment=dev at 7pm
aws ec2 stop-instances --instance-ids $(aws ec2 describe-instances \
  --filters "Name=tag:Environment,Values=dev" "Name=instance-state-name,Values=running" \
  --query 'Reservations[].Instances[].InstanceId' --output text)

Use AWS Instance Scheduler, Azure Start/Stop VMs, or a simple cron + Lambda. Most teams save $2,000-$15,000/month on this alone.

---

2. 🧹 Kill Orphaned Resources (Savings: 5-15% of total bill | Effort: Low)

Every cloud account accumulates waste: unattached EBS volumes, old snapshots, idle load balancers, unused Elastic IPs, abandoned RDS instances.

Checklist to run right now:

• Unattached EBS volumes → aws ec2 describe-volumes --filters "Name=status,Values=available"

• Snapshots older than 90 days with no AMI dependency

• Elastic IPs not associated with running instances

• Load balancers with zero healthy targets

• Idle RDS instances (0 connections for 14+ days)

I've seen teams find $5K-$50K/month in orphaned resources on the first sweep.

---

3. 📐 Rightsize Compute Instances (Savings: 30-50% | Effort: Medium)

The average cloud instance runs at 15% CPU utilization. That means most instances are 3-5x larger than they need to be.

How to do it:

1. Pull 14 days of CPU + memory metrics from CloudWatch / Azure Monitor / Cloud Monitoring

2. Use AWS Compute Optimizer, Azure Advisor, or GCP Recommender for automated suggestions

3. Target instances consistently below 30% CPU — they're almost always candidates for downsizing

4. Test one size down, validate for a week, then move to the next batch

Pro tip: Don't just downsize — check if a different instance family is better. A memory-optimized r6g.large might outperform a general m5.xlarge at half the cost for your workload.

---

4. 💰 Commit to Reserved Instances / Savings Plans (Savings: 30-72% | Effort: Medium)

If you have stable baseline workloads (and most production environments do), you're leaving money on the table by paying on-demand rates.

Decision framework:

• Savings Plans (AWS) → Best flexibility, covers EC2 + Fargate + Lambda

• Reserved Instances → Higher discount for specific instance types you won't change

• GCP CUDs → Spend-based for flexibility, resource-based for maximum discount

• Azure Reservations → 1-year or 3-year, can be exchanged if needs change

Golden rule: Only commit on workloads that have been stable for 3+ months. Start with 1-year terms. Never commit more than 80% of your baseline.

---

5. 🏗️ Migrate gp2 → gp3 EBS Volumes (Savings: 20% | Effort: Low)

This is free money. AWS gp3 volumes are 20% cheaper than gp2 with better baseline performance (3,000 IOPS vs 100 IOPS/GB). There is almost no reason to stay on gp2.

# Find all gp2 volumes
aws ec2 describe-volumes --filters "Name=volume-type,Values=gp2" \
  --query 'Volumes[].[VolumeId,Size,State]' --output table

# Modify to gp3 (online, no downtime)
aws ec2 modify-volume --volume-id vol-xxxxx --volume-type gp3

Migration is online — zero downtime. A team with 100 gp2 volumes typically saves $500-$2,000/month instantly.

---

The Compound Effect

These 5 optimizations alone can reduce your cloud bill by 30-50%. The key is to do them systematically, not as a one-time cleanup.

Build a monthly review cadence, assign ownership, and track savings over time. Cloud cost optimization isn't a project — it's a practice.

---

Want the full playbook? CloudSave Academy covers these techniques and 16 more across 6 chapters — from billing analysis to automated governance. Every lesson includes provider-specific implementations for AWS, Azure, and GCP.