Based on the billing data you provided, we identified 4 areas of avoidable spend. If the recommendations below are applied, we estimate you could save around $1,150 per month (≈ $13,800 per year). This is an estimate based on your usage patterns; actual savings depend on your workload.
Top services by monthly cost (from your CSV):
| Service | Monthly cost | % of total |
|---|---|---|
| EC2 (compute) | $2,100 | 49% |
| RDS (database) | $980 | 23% |
| S3 (storage) | $540 | 13% |
Each finding is sorted by estimated monthly impact. Risk reflects how careful you should be when applying the fix.
| Finding | Current cost | Recommended action | Risk | Est. saving |
|---|---|---|---|---|
| Idle / stopped EC2 with attached EBS 3 instances stopped > 30 days but still billed for storage |
$680 | Terminate instances and release unattached EBS volumes; or schedule off-hours stop/start | Low | $680 |
| Over-provisioned RDS instance db.r5.large averaging 8% CPU — far larger than needed |
$420 | Downsize to db.t3.medium after a 1-week CPU watch; keep Multi-AZ only if required | Medium | $240 |
| S3 no lifecycle policy Old versions and incomplete multipart uploads never expire |
$180 | Add a lifecycle rule to expire non-current versions after 30 days and abort failed uploads | Low | $120 |
| No Compute Savings Plan Steady-state EC2 spend is billed on-demand |
$300 | Purchase a 1-year Compute Savings Plan covering ~70% of steady EC2 usage | Medium | $110 |
Additional lower-impact findings: 2 unattached Elastic IPs ($7/mo), 1 NAT gateway in an unused VPC ($32/mo).