Cloud Cost Optimization: How to Save 40% on Your AWS Bill

The average organization wastes 30-35% of their cloud spend. For a company spending $100,000/month on AWS, that is $360,000-$420,000 per year going straight to waste. After optimizing dozens of AWS environments, here are the proven strategies that consistently deliver 40%+ savings.

Strategy 1: Rightsizing (10-15% Savings)

Rightsizing means matching your instance types to actual workload requirements. Most organizations over-provision because developers choose instance sizes based on peak load estimates rather than actual usage data.

Action Plan:

1. Enable AWS Compute Optimizer (it is free)
2. Review recommendations weekly for 30 days
3. Downsize instances with average CPU utilization below 40%
4. Consider Graviton (ARM) instances for 20-40% better price-performance

A common finding: teams running m5.xlarge instances that could run on m7g.large with better performance at half the cost.

Strategy 2: Reserved Instances and Savings Plans (20-30% Savings)

If you have steady-state workloads (databases, application servers, CI/CD runners), commit to 1-year or 3-year Reserved Instances or Savings Plans. The math is straightforward:

• 1-year, no upfront: ~30% savings
• 1-year, all upfront: ~40% savings
• 3-year, all upfront: ~60% savings

Start with Compute Savings Plans — they offer the same discounts as Reserved Instances but with more flexibility across instance families and regions.

Strategy 3: Spot Instances (60-90% Savings)

Spot instances offer spare AWS capacity at up to 90% discount. They can be interrupted with 2 minutes notice, so they are ideal for:

• CI/CD build runners
• Batch processing and data pipelines
• Dev/test environments
• Kubernetes worker nodes (with proper pod disruption budgets)

Use Spot Fleet or Karpenter (for EKS) to automatically manage spot instance lifecycle.

Strategy 4: Storage Optimization (5-15% Savings)

Storage costs are often the second-largest line item on AWS bills:

• S3 Intelligent-Tiering: Automatically moves objects between access tiers
• S3 Lifecycle Policies: Archive to Glacier after 90 days, delete after 365 days
• EBS Optimization: Delete unattached volumes, snapshot and delete unused volumes, use gp3 instead of gp2
• Delete old snapshots: Many organizations have thousands of forgotten snapshots

Strategy 5: Database Optimization (5-10% Savings)

RDS is typically the third-largest cost center:

• Use Aurora Serverless v2 for variable workloads (scales to zero)
• Enable RDS Reserved Instances for steady-state databases
• Right-size RDS instances (most are over-provisioned)
• Consider DynamoDB on-demand for unpredictable workloads

Strategy 6: Implement FinOps Practices

Cost optimization is not a one-time project — it is a continuous practice:

• Tagging: Tag every resource with team, environment, and project
• Budgets: Set AWS Budgets with alerts at 50%, 80%, and 100%
• Anomaly Detection: Enable AWS Cost Anomaly Detection
• Weekly Reviews: Review Cost Explorer weekly with engineering leads
• Showback/Chargeback: Make teams accountable for their cloud spend

Quick Wins Checklist

Implement these today for immediate savings:

1. Turn off dev/test environments outside business hours (save 65%)
2. Delete unattached EBS volumes and old snapshots
3. Terminate idle load balancers and NAT gateways
4. Switch from gp2 to gp3 EBS volumes (20% cheaper, better performance)
5. Enable S3 Intelligent-Tiering on all buckets

Every dollar saved on cloud infrastructure is a dollar available for innovation. Our free FinOps and cloud optimization courses teach you how to build a culture of cost-conscious engineering.

Kehinde Ogunlowo

Senior Multi-Cloud DevSecOps Architect & AI Engineer

11+ years at Fortune 500 companies including Cigna and Lockheed Martin. AWS/Azure/GCP certified. Founder of Citadel Cloud Management.