Cost Optimization Hub now supports stopping idle Amazon EC2 instances

Posted on: Nov 17, 2026

AWS Cost Optimization Hub now lets you stop idle Amazon EC2 instances directly from your recommendations. Cost Optimization Hub consolidates and prioritizes cost optimization recommendations across your AWS accounts and Regions, including idle resources. Previously, stopping an idle instance required you to leave Cost Optimization Hub and identify the specific instance in the Amazon EC2 console. Now you can stop it from the Savings opportunities page in Cost Optimization Hub.

When you choose Stop next to an idle instance recommendation, a confirmation shows the instance, its account and Region, what the instance loses when it stops, such as instance store data and data in memory, and what continues to bill, such as EBS volumes and Elastic IP addresses. Stopping does not terminate the instance or delete its EBS volumes, and you can start it again from the EC2 console. Stop needs no separate setup and uses your existing permissions. To receive idle resource recommendations, turn on Cost Optimization Hub and AWS Compute Optimizer.

This feature is available at no additional charge in all AWS Regions except the AWS GovCloud (US) Regions and the China Regions.

To get started, open Cost Optimization Hub in the AWS Billing and Cost Management console and go to Savings opportunities. To learn more, see the Cost Optimization Hub product page and user guide.