Skip to main content

EC2 Low Utilization Instance Remediation Tutorial

Overview​

This tutorial walks through terminating an EC2 instance identified as having near-zero CPU utilization (<5%) and minimal network activity (<5MB/day) over 30 days, indicating it is likely unused.

Policy: ec2-low-utilization Remediation Action: Terminate instance Target Service: EC2

Cost Impact​

Immediate Savings:

  • Eliminates ongoing compute charges (hourly instance cost) and typically associated EBS storage costs
  • Exact savings depend on instance type — for example, a t3.medium running 24/7 costs approximately ~$30/month

Prerequisites​

  • Access to AWS Console with EC2 permissions
  • Instance ID of the low-utilization instance to terminate

Step 1: Navigate to EC2 Instances Console​

Navigate to the EC2 Instances console at https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#Instances:

Step 2: Search for the Flagged Instance​

In the search bar at the top of the instances table, enter the instance ID i-0c7ae58c8942aea3b to locate the flagged instance.

Step 3: Review Instance Details​

Click on the instance to select it. Review the instance details in the panel below to confirm it matches the flagged resource — note the instance type, launch time, and current state.

Step 4: Verify Low Utilization via CloudWatch Metrics​

Click the Monitoring tab in the instance details panel to review CloudWatch metrics. Verify that CPU utilization has been consistently below 5% and network traffic is minimal over the past 30 days. This confirms the instance is genuinely idle and safe to terminate.

Step 5: Open Instance State Menu​

With the instance selected, click the Instance state dropdown button at the top of the page.

Step 6: Select Terminate Instance​

Select Terminate instance from the dropdown menu.

Step 7: Confirm Termination​

A confirmation dialog will appear warning that termination is permanent. Review the instance ID to ensure it is correct, then click Terminate to proceed.

Step 8: Verify Termination​

The instance state will change to Shutting down and then Terminated. The instance's EBS volumes will be deleted automatically if they were configured with "Delete on Termination" enabled (the default). You can verify this in the Storage tab.

Alternative Approaches​

1. Stop the Instance​

Stop the instance instead of terminating if you want to preserve the instance configuration and EBS volumes for potential future use. You'll still pay for EBS storage but not compute.

2. Right-Size the Instance​

Right-size the instance to a smaller type if it does have some legitimate workload but is over-provisioned.

3. Create an AMI Before Terminating​

Create an AMI before terminating if you may need to recreate the instance later with the same configuration and data. Use Actions → Image and templates → Create image.

Summary​

By terminating idle EC2 instances with consistently low utilization, you:

  • Eliminate 100% of compute charges for the instance
  • Remove associated EBS storage costs (if delete-on-termination is enabled)
  • Reduce resource clutter and simplify management
  • Maintain compliance with cost optimization policies