Docs/Schedules

Schedules

Configure when your RDS instances should be running or stopped.

How it works

SnoozeDB uses a CRON engine that regularly checks the state of each active instance. If an instance is running outside its scheduled hours, it is stopped. If it is stopped during its active hours, it is started.

Operations are idempotent: if an instance is already in the expected state, no action is taken.

Business Hours

Business Hours mode is the most common. It keeps your instances running Monday through Friday during work hours and stops them at night and on weekends.

Monday–Friday:  08:00 ──── ON ──── 20:00
                20:00 ──── OFF ─── 08:00

Saturday–Sunday: ───────── OFF ──────────

With standard Business Hours (8am–8pm, Mon–Fri), you save approximately 65% of the instance's on-demand cost.

Custom schedules

For specific needs, you can create a fully custom schedule:

Define different time slots for each day of the week
Configure instances running only on certain days (e.g. Monday to Wednesday)
Combine with holidays or maintenance windows

Timezones

Schedules are configured in your chosen timezone. If your team is in Europe/Paris, business hours correspond to CET/CEST automatically, including during daylight saving time changes.

Multi-timezone teams

For teams spread across multiple timezones, create multiple organizations or use custom schedules with extended time slots.

Start / Stop behavior

Stop: SnoozeDB sends an rds:StopDBInstance. The instance transitions to "stopping" then "stopped". Storage remains intact, only compute is stopped.

Start: SnoozeDB sends an rds:StartDBInstance. The instance restarts with its configuration and data intact. Startup time depends on instance size (typically 2-5 minutes).

Important: AWS automatically restarts instances that have been stopped for 7 days. SnoozeDB will stop them again at the next CRON cycle if they are outside their schedule.