How to Migrate from AWS Instance Scheduler to ZopNight: Step by Step

Move from AWS Instance Scheduler tag-based on/off rules to ZopNight cron schedules. Multi-cloud coverage, dependency ordering, and one-click overrides on top.

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 45 minutes. Before you start you will want: AWS Instance Scheduler installed; A list of current schedule tags and instance assignments; A ZopNight account.

The steps

1. Inventory current Instance Scheduler tags.
2. Connect AWS to ZopNight.
3. Recreate the schedules.
4. Attach resources via tags or groups.
5. Run side by side, then disable Instance Scheduler.
6. Add overrides and notifications.

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 guide covers where it fits, and the AWS EC2 scheduling 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.