AWS Compute Optimizer now supports EC2 instances with non-consecutive utilization data

AWS Compute Optimizer no longer requires EC2 instances to have 30 consecutive hours of utilization data to generate recommendations. EC2 instances that have non-consecutive 30 hours of utilization data during the 14 days period (for EC2 instances without enhanced infrastructure metrics) or up to 93 days (for EC2 instances with enhanced infrastructure metrics) can get cost and performance optimization recommendations.

With today’s launch, you can unlock additional savings and performance improvement opportunities for your EC2 instances running scheduled workloads or if they have stopped in the look back period. Compute Optimizer now generates rightsizing recommendations for every EC2 instance type it currently supports if an EC2 instance has accumulated more than 30 hours of utilization data during the data collection period. You no longer have to worry about not having visibility into savings or performance improvement opportunities if your EC2 instances were stopped during the data collection period.

Compute Optimizer support for these instances is available in a total of 21 AWS Regions, including the US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Asia Pacific (Osaka), Asia Pacific (Hong Kong), Middle East (Bahrain), Africa (Cape Town), Europe (Milan), and South America (São Paulo) Regions.

To learn more about the new feature updates, please visit Compute Optimizer’s product page and user guide.