Amazon Compute Optimizer recommends optimal Amazon Web Services resources for your workloads to reduce costs and improve performance by using machine learning to analyze historical utilization metrics. With the default version of Compute Optimizer, you only pay for the Amazon Elastic Compute Cloud (EC2) instances, Amazon Elastic Block Store (EBS) volumes, Amazon Lambda functions, and Amazon Elastic Container Service (ECS) services on Amazon Fargate you use to run your applications and for Amazon CloudWatch monitoring fees. The default Compute Optimizer option analyzes your Amazon CloudWatch metrics for the last 14 days to provide recommendations.
To receive EC2 or Auto Scaling group recommendations that capture monthly or quarterly utilization patterns, you can activate Compute Optimizer enhanced infrastructure metrics – a paid feature. With the feature activated, Compute Optimizer ingests and analyzes up to six times more Amazon CloudWatch utilization metrics history than the default Compute Optimizer option (up to 3 months of history vs. 14 days). Enhanced infrastructure metrics costs CNY0.002135786 per resource per hour and is charged based on the number of hours per month the resource is running. The feature would cost CNY1.589025 per resource per month for resources running a full 31-day month.
Pricing Table
| Enhanced infrastructure metrics for EC2 | CNY0.002135786 resource/hour based on the number of hours a resource is running per month |
Pricing examples
Example 1: Customer activates enhanced infrastructure metrics for 5 EC2 instances on July 15. EC2 instances are running throughout the entire month (744 hours).
Let’s say you’ve activated enhanced infrastructure metrics on 5 resources on July 15. Compute Optimizer will charge you for activating enhanced infrastructure metrics just for those 5 resources during the time that the resources ran. Assuming the resources ran for 31 days (744 hours), the bill at the end of the month for Compute Optimizer would be calculated as follows:
| Usage type | Number of resources | Hours resources are running | Billable Hours | Hourly Charge | Monthly charge |
| Enhanced infrastructure metrics | 5 | 744 | 744 | CNY0.002135786 | 5*744* CNY0.002135786 = CNY7.9451239 |
Example 2: Customer activates enhanced infrastructure metrics for a fixed size (4) Auto Scaling group. The number of distinct EC2 instances that ran within the Auto Scaling group in July was 5.
Let’s say you’ve activated enhanced infrastructure metrics for a fixed size 4-instance Auto Scaling group. Compute Optimizer will charge you for activating enhanced infrastructure metrics just for the instances that ran within that Auto Scaling group during that month. Assuming 3 resources ran for 31 days (744 hours) and 2 ran for half the month (372 hours), the bill at the end of the month for Compute Optimizer would be calculated as follows:
| Usage type | Number of resources | Hours resources are running | Billable Hours | Hourly Charge | Monthly charge |
| Enhanced infrastructure metrics | 3 | 744 | 744 | CNY0.002135786 | 3*744* CNY0.002135786= CNY4.7670744 |
| Enhanced infrastructure metrics | 2 | 372 | 372 | CNY0.002135786 | 2*372* CNY0.002135786= CNY1.5890248 |
| Total = CNY 6.3561024 | |||||
Example 3: Customer activates enhanced infrastructure metrics for 5 EC2 instances on June 20. The 5 instances run for only 15 days (360 hours).
Let’s say you’ve activated enhanced infrastructure metrics on 5 instances on June 20. Compute Optimizer will charge you for activating enhanced infrastructure metrics just for those 5 instances and charge you for the number of hours those instances ran. Assuming that the resources ran for only 15 days (360 hours), the bill at the end of that month for Compute Optimizer would be calculated as follows:
| Usage type | Number of resources | Hours resources | Billable Hours | Hourly charge | Monthly charge |
| Enhanced infrastructure Metrics | 5 | 360 | 360 | CNY0.002135786 | 5*360* CNY0.002135786= CNY3.844415 |
