Analyze Savings-Plan-eligible compute usage (EC2, Fargate, and Lambda) in an AWS account to determine whether it is a good fit for a Savings Plan commitment. This plan reviews recent usage and cost patterns, captures existing Savings Plans and Reserved Instance coverage, excludes workloads that are poor commitment candidates, evaluates stability with a conservative usage floor, and produces an account-level verdict with a machine-readable result block.
Collect eligible compute usage and cost data
Gathers recent EC2, Fargate, and Lambda compute usage, cost, existing commitment coverage, and CloudWatch utilization signals to establish the baseline consumption pattern that should be evaluated for Savings Plans.
Exclude non-commitment candidates
Identifies workloads that should not be included in commitment sizing because they appear idle, temporary, schedulable, burst-only, likely to be rightsized, or likely to change.
Analyze consumption patterns for commitment fit
Reviews usage stability at the finest granularity available (hourly when enabled, daily minimums otherwise), variance, seasonality, concentration risk, and usage flexibility across Regions, instance families, container workloads, and operating systems.
Estimate Savings Plan opportunity
Builds conservative, target, and upper-bound commitment estimates, compares Compute Savings Plans and EC2 Instance Savings Plans fit, and calls out expected savings and overcommitment risk.