A SysOps Administrator is reviewing optimization recommendations in AWS Compute Optimizer for a fleet of EC2 instances hosting a memory-intensive batch processing application. The dashboard lists these instances as over-provisioned based on CPU utilization, but memory metrics are missing from the analysis, leading to potentially inaccurate right-sizing recommendations. Which action must the administrator take to enable AWS Compute Optimizer to ingest memory utilization metrics for these EC2 instances?
- Install and configure the unified CloudWatch agent on the EC2 instances to publish OS-level memory metrics to Amazon CloudWatch under the CWAgent namespace.Cevap
- BEnable CloudWatch detailed monitoring on the EC2 instances to increase the reporting frequency of CPU and memory metrics to one-minute intervals.
- CConfigure an AWS Budgets alert to monitor instance memory utilization and send a notification when usage exceeds 80%.
- DEnable cost allocation tags in the Billing Console and use AWS Cost Explorer to analyze memory utilization patterns across instance families.
Cevap
Install and configure the unified CloudWatch agent on the EC2 instances to publish OS-level memory metrics to Amazon CloudWatch under the CWAgent namespace.
The correct answer is to install and configure the unified CloudWatch agent on the EC2 instances to publish memory metrics to the default CWAgent namespace. Because memory utilization is an operating system-level metric, the underlying AWS hypervisor does not have visibility into it. The unified CloudWatch agent must be installed to collect memory metrics and send them to CloudWatch, where AWS Compute Optimizer can retrieve and ingest them to deliver memory-aware right-sizing recommendations.
Adım Adım Çözüm
Anahtar Kavram
AWS Compute Optimizer relies on the unified CloudWatch agent to analyze memory metrics because memory is an operating system-level metric not visible to the hypervisor by default.
Tahmini Süre:1m 30s