# Schedule AWS EC2 Instances: Stop Paying for Idle VMs > ZopNight schedules EC2 Instances on AWS to run on your team's hours and stop the rest of the time. Read-only setup, dependency-aware, production excluded by default. Source: https://zop.dev/zopnight/aws/ec2 Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, aws, compute, scheduling --- Most of what teams spend on EC2 Instances in non-production is spent while nobody is watching. In a development, staging, or QA account these resources are billed for every hour they exist, but the people who use them work a fraction of those hours. Nights, weekends, holidays, and the long tail of "we'll get back to that environment next sprint" all meter at full price. ZopNight closes that gap by scheduling your EC2 Instances to run on your team's hours and stop the rest of the time, without touching your data and without a migration. It is the most direct lever in [FinOps](https://zop.dev/learn/finops), and for teams comparing tools it is where ZopNight pulls ahead of dashboard-first platforms like [CloudHealth](https://zop.dev/compare/cloudhealth-vs-zopnight). ## Why EC2 Instances cost more than they should Cloud providers bill EC2 Instances by the hour whether or not anyone is using them, and most non-production fleets default to running 24/7 out of habit rather than need. At typical on-demand rates ($0.02–$3.00/hr) an always-on instance quietly bills the same on a Tuesday afternoon as it does at 3 AM on a Sunday. Here is the shape of it. Say a box runs at a typical on-demand rate of $0.17 an hour. Left on around the clock that is about $124 a month, because a month is roughly 730 hours. Confine it to a single-shift work week, about 50 hours, and you pay for 50 hours instead of 730. Your own rate and hours will differ, but the ratio is the point: in non-production, most of the meter runs while nobody is working. The instinct is usually to reach for a smaller instance type. But rightsizing only helps a resource that is genuinely too big; it does nothing for a correctly-sized resource that simply runs when no one is around. The larger, easier win is refusing to pay for the hours nobody is working, and it carries none of the performance risk of down-sizing a box that might spike tomorrow. ## Stopping and starting EC2 Instances safely ZopNight handles the Stop/Start via AWS EC2 API on every EC2 Instances in scope, in dependency order so nothing comes up before what it depends on. A scheduled stop preserves your data exactly as a normal power-off would; ZopNight never terminates or deletes the resource, and idle detection watches CPU, network, and disk signals to surface the EC2 Instances that are running but doing nothing. In practice the setup is: Connect your AWS account with read-only IAM role; ZopNight discovers all EC2 instances across regions; Create a schedule (e.g., stop at 7 PM, start at 8 AM weekdays); ZopNight executes stop/start via EC2 API, dependencies respected. If you run EC2 Instances you probably also run [RDS](https://zop.dev/zopnight/aws/rds), [EKS](https://zop.dev/zopnight/aws/eks), [Auto Scaling Groups](https://zop.dev/zopnight/aws/auto-scaling-groups), and scheduling them together is where the dependency ordering earns its keep. Related reading: [scheduling](https://zop.dev/solutions/scheduling) and [idle detection](https://zop.dev/solutions/idle-detection). ## How ZopNight schedules EC2 Instances The loop that does this is deliberately mechanical, and it starts read-only. You connect AWS with a read-only role, and ZopNight discovers every EC2 Instances across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled. Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like "dev-cluster" or "staging-db" so a whole environment follows one cadence. Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a EC2 Instances ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it. ## Getting started Getting started is intentionally low-stakes: - Connect AWS with a read-only role. Nothing is scheduled or changed at this stage. - Let ZopNight discover your EC2 Instances and review exactly what it found, filtered by account, region, and status. - Create a schedule in your timezone and attach the non-production resources or groups you want it to cover. - Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing. Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action. ## Frequently asked questions ### Does stopping EC2 instances delete my data? No. Stopping an EC2 instance preserves all EBS volumes and data. It only stops the compute, your data is safe. ZopNight never terminates or deletes instances. ### Can I override the schedule for a specific instance? Yes. ZopNight supports one-click overrides that force an instance ON or OFF for a defined time window, with automatic expiry. ### Does ZopNight support Auto Scaling Groups? Yes. ZopNight can scale ASG desired capacity to zero on schedule and restore it on start, coordinating with the EC2 instances in the group. ### What happens if an instance fails to stop? ZopNight retries automatically up to 3 times. If the action still fails, it sends a notification to your configured Slack, Teams, or webhook channel.