Analyze Database-Savings-Plan-eligible usage in one AWS account to determine whether the supplied provider commitment is safe and economically justified. The plan separates eligible recurring usage from unrelated database charges, reviews existing commitment coverage, uses engine-specific inventory and CloudWatch evidence to exclude temporary, idle, schedulable, or likely-to-change capacity, and produces conservative commitment guidance with a machine-readable verdict.
Collect eligible database usage and coverage
Establishes a 7-, 30-, and preferably 60- or 90-day cost baseline by service, usage type, operation, Region, and purchase model.
Validate database workload persistence
Inventories material database resources and checks engine-appropriate utilization, capacity, runtime, scaling, topology, and lifecycle evidence.
Exclude poor commitment candidates
Removes usage likely to be eliminated through rightsizing, scheduling, deletion, migration, topology reduction, or other near-term change.
Estimate Database Savings Plan fit
Sizes conservative and target hourly commitments from the stable uncovered eligible floor and compares them directly with the provider recommendation.