# How to Schedule AWS EC2 Start/Stop: Step by Step

> How to Schedule AWS EC2 Start/Stop. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/schedule-aws-ec2-start-stop
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Step-by-step guide to scheduling AWS EC2 instance start and stop times with ZopNight. Reduce non-production EC2 costs meaningfully in under 5 minutes.

This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 5 minutes. Before you start you will want: An AWS account with EC2 instances running; Permission to create an IAM role; A ZopNight account (free tier available).

## The steps

1. Connect your AWS account.
2. Review discovered EC2 instances.
3. Create a schedule.
4. Assign resources to the schedule.
5. Enable and verify.

## Why this is safe to do today

The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.

If you want the fuller context behind this task, the [FinOps](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) page shows the same loop applied to a specific resource.

## Getting started

Getting started is intentionally low-stakes:

- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources 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 preserves all EBS volumes and data. ZopNight never terminates instances, it only stops and starts them.

### Can I override the schedule if I need instances running late?

Yes. ZopNight supports one-click overrides with automatic expiry so you never forget to re-enable the schedule.