# Missing scheduled shutdown for non-production EC2 instances Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-scheduled-shutdown-for-non-production-ec2-instances Non-production EC2 instances are often provisioned for daytime-only usage but remain running 24/7 out of convenience or oversight. By: Yulia Perlis Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Missing Scheduled Shutdown for Non-Production EC2 Instances The short version Non-production EC2 instances are often provisioned for daytime-only usage but remain running 24/7 out of convenience or oversight. Yulia Perlis AWS service [AWS EC2](https://www.pointfive.co/efficiency-hub/cloud-services/aws-ec2) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0096 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. This results in unnecessary compute charges, even if the workload is inactive for 16+ hours per day. AWS supports automated schedules to stop and start instances at predefined times, allowing organizations to retain data and instance configuration without paying for unused runtime. Implementing a shutdown schedule for inactive periods (e.g., nights, weekends) can reduce compute costs by up to 60% in typical non-prod environments. ## Billing model The pricing dimensions that drive this cost. EC2 is billed per second with a 60-second minimum (Linux, Windows, RHEL and Ubuntu Pro; SLES is billed per full hour) based on: - Instance type and size - Uptime duration - Additional charges for associated resources (e.g., EBS volumes) continue even when the instance is stopped ## How to detect 4 checks to find it in your estate. - Identify EC2 instances in dev/test/staging environments using tags or naming conventions - Analyze instance runtime patterns via CloudWatch metrics or billing data - Highlight instances with predictable daily usage but continuous uptime - Determine whether workloads require persistent availability outside working hours ## How to fix 4 ways to remove the waste. - Implement scheduled shutdowns using Instance Scheduler on AWS or EventBridge rules - Ensure stateful data is retained via attached EBS volumes or AMIs - Set start/stop windows aligned to working hours (e.g., 8 a.m.-6 p.m. weekdays) - Review and optimize schedules quarterly to match evolving team usage ## Documentation Vendor references for pricing and configuration. - [Instance Scheduler on AWS - Automate starting and stopping AWS instances docs.aws.amazon.com](https://docs.aws.amazon.com/solutions/latest/instance-scheduler-on-aws/solution-overview.html) - [Stop and start Amazon EC2 instances docs.aws.amazon.com](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS EC2 CER-0327 ### [Spot Instance Overreliance Without Effective Cost-Per-Performance Analysis](https://www.pointfive.co/efficiency-hub/inefficiencies/spot-instance-overreliance-without-cost-per-performance-analysis) Organizations frequently pursue aggressive Spot Instance adoption based on headline discount percentages - up to 90% off On-Demand pricing - without evaluating the effective cost per unit of work completed. While Spot pricing can deliver... Compute - AWS EC2 CER-0211 ### [Unnecessary Multi-AZ Deployment for Non-Production EC2 Instances](https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-multi-az-deployment-for-non-production-ec2-instances) Multi-AZ deployment is often essential for production workloads, but its use in non-production environments (e.g., development, test, QA) offers minimal value. These environments typically do not require high availability, yet still incur... Compute - AWS EC2 CER-0344 ### [Burstable EC2 Instances Incurring Unlimited Mode Surplus Credit Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/burstable-ec2-instances-incurring-unlimited-mode-surplus-credit-charges) Burstable performance instances (the T family) are priced for workloads that run below a baseline CPU level most of the time. T3, T3a, T4g and T8i instances launch in unlimited mode by default, which lets them burst above the baseline for... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.