中文
devexamples
← Workflows

阅读中文版本

Cloud Spend Review Workflow

Break down spend by service and owner, find idle and oversized resources, act on the biggest wins, and track savings realized not just identified.

intermediate~90 mincostcloudoperations

Objective

Reduce cloud cost through owner-aware review and verified savings rather than untracked recommendations.

Environment

  • Billing data with tags and account mapping
  • Resource utilization metrics

Steps

1. Break down spend by service, environment,

Break down spend by service, environment, and owner.

Expected state: Costs are attributable.

2. Find idle, oversized, and orphaned resources

Find idle, oversized, and orphaned resources.

Expected state: Waste is identified with evidence.

3. Act on the largest opportunities

Act on the largest opportunities with owners.

Expected state: Changes actually happen.

4. Track realized savings against the changes

Track realized savings against the changes made.

Expected state: Savings are verified, not assumed.

Decision points

Rightsize or delete idle?

  • Delete confirmed orphans
  • Rightsize first

Delete confirmed orphans; rightsizing something nobody uses just makes waste cheaper.

Charge costs back or show centrally?

  • Show to owners
  • Central only

Show per owner; without visibility the owners who could fix waste have no reason to.

Expected outcome

Reduced cloud spend with attributable costs, acted-on opportunities, and tracked realized savings.

Verification

Confirm the next billing cycle shows the expected reduction and that no removed resource was actually needed.

Cleanup

Record the changes, owners, and verified savings for the next review.

Overview

Reduce cloud cost through owner-aware review and verified savings rather than untracked recommendations. Confirm the next billing cycle shows the expected reduction and that no removed resource was actually needed.

Steps

  1. Break down spend by service, environment, and owner. Expected state: Costs are attributable.
  2. Find idle, oversized, and orphaned resources. Expected state: Waste is identified with evidence.
  3. Act on the largest opportunities with owners. Expected state: Changes actually happen.
  4. Track realized savings against the changes made. Expected state: Savings are verified, not assumed.
# top services by cost
aws ce get-cost-and-usage --time-period Start=2026-09-01,End=2026-10-01 \
  --granularity MONTHLY --metrics UnblendedCost --group-by Type=DIMENSION,Key=SERVICE

Verification

  • Reduced cloud spend with attributable costs, acted-on opportunities, and tracked realized savings.

Decision points

  • Rightsize or delete idle? Options: Delete confirmed orphans; Rightsize first. Recommended: Delete confirmed orphans; rightsizing something nobody uses just makes waste cheaper.
  • Charge costs back or show centrally? Options: Show to owners; Central only. Recommended: Show per owner; without visibility the owners who could fix waste have no reason to.