EC2 Missing Memory Metrics

Opportunity Name:

EC2 Missing Memory Metric Finder

AWS Resource Type:

Amazon Elastic Compute Cloud (EC2)

Opportunity Description:

This Finder identifies EC2 instances that are not configured to report memory utilization metrics to Amazon CloudWatch. Without these metrics, customers lack critical visibility into instance-level memory usage, which is essential for effective rightsizing and cost optimization.

Criteria for Identifying the Opportunity:

An EC2 instance is flagged if it does not have memory utilization metrics visible in Amazon CloudWatch. This typically indicates that the CloudWatch Agent is either not installed or not configured correctly to collect memory data from the instance.

Potential Savings (range in % on annual basis):

This Finder does not directly generate savings. However, enabling memory metrics provides the data required to make informed decisions around rightsizing EC2 instances — which can then lead to substantial indirect cost savings.

What Happens When the Fixer is Executed?

There is no automated Fixer for this opportunity. To resolve the issue, customers need to manually install and configure the CloudWatch Agent on each identified EC2 instance.

This process involves:

1. Installing the required dependencies and the CloudWatch Agent package.
2. Configuring the agent to collect memory metrics.
3. Starting the agent to begin streaming metrics to CloudWatch.

You can follow AWS's step by step instructions here:
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html

Is it Possible to Roll Back Once CloudFix Implements the Fixer?

Not applicable — there is no Fixer. However, users can stop or remove the CloudWatch Agent at any time if needed.

Can CloudFix Implement the Fix Automatically Once I Accept the Recommendation?

No — this is a manual process. CloudFix identifies the opportunity, but it does not automate the installation or configuration of the CloudWatch Agent.

Does This Fix Require Downtime?

No — installing and configuring the CloudWatch Agent does not disrupt the instance or require downtime.