Analyze EC2 usage 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, excludes workloads that are poor commitment candidates, evaluates stability and flexibility, and summarizes the expected opportunity with supporting evidence.
Collect EC2 usage and cost data
Gathers recent EC2 compute usage, cost, 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 hourly and daily usage stability, variance, seasonality, concentration risk, and usage flexibility across Regions, instance families, operating systems, and workload groups.
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.