Skip to content
Nubent

/AWS · Nov 17, 2026

Cost Optimization Hub now stops idle EC2

You can now stop idle EC2 instances straight from Cost Optimization Hub recommendations, without going to the EC2 console, and see up front what you lose and what keeps billing.

What changes

Cost Optimization Hub brings together savings recommendations from all your accounts and Regions. Now each idle instance comes with an option to stop it. The confirmation shows the account, the Region, what you lose when you stop it (instance store and in-memory data) and what keeps billing, such as EBS volumes and Elastic IPs. It doesn't terminate the instance or delete its volumes, and there's no additional cost.

How to implement it

  1. Turn on Cost Optimization Hub and AWS Compute Optimizer to get idle resource recommendations.

  2. Review opportunities by account and check with each team before stopping anything.

  3. Tag instances with owner and environment so decisions are quick.

  4. After stopping, review the EBS volumes and Elastic IPs that keep billing.

Nubent's take

Stopping instances by hand is a patch. The real savings come from understanding why those instances were left running and automating shutdown for non-production environments.

Next step

Should we implement it in your account?

We check whether it fits, how much work it takes and what risks it carries. 30 minutes with an engineer.