![]() ![]() This rule can help you work with the AWS Well-Architected Framework. This rule can help you with the following compliance standards:įor further details on compliance standards supported by Conformity, see here. The console also provides information about each EC2 instance marked as underutilized, details such as region, ID, instance type, launch time, operating system and more in order to help you perform the right-sizing analysis. EC2MemoryUtilization) and use a custom name for this metric. You can also change the default name for the memory utilization metric (i.e. ![]() Note: You can change the default threshold values for this rule on the Trend Micro Cloud One™ – Conformity console and set your own values for the CPU (percent), memory utilization (percent) and the preferred number of days for each condition to configure a custom underuse level for your Amazon EC2 instances. The instructions required for installing the monitoring agent, based on the Operating System (OS) used by the instance, are available at this URL. By default, Amazon CloudWatch can't record an EC2 instance memory utilization because the necessary metric cannot be implemented at the hypervisor level, therefore to be able to report the memory utilization using CloudWatch you need to install an agent on the instance that you want to monitor and create a custom metric (we'll name it EC2MemoryUtilization) on the Amazon CloudWatch console. The average memory utilization has been less than 60% for the last 7 days.The average CPU utilization has been less than 60% for the last 7 days.By default, an Amazon EC2 instance is considered "underutilized" when matches the following criteria (to declare the instance "underutilized" both conditions must be met): ![]() Identify any Amazon EC2 instances that appear to be underutilized and downsize (resize) them to help lower the cost of your AWS bill. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |