Introduction
Uptime Scheduler automatically starts and stops your AWS resources on a schedule, so you only pay for compute when you need it.
How it works
Uptime Scheduler uses AWS tags to define when resources should run. Tag a resource with uptime:schedule and Uptime Scheduler handles the rest — no scripts, no cron jobs, no maintenance.
uptime:schedule = 9-17 mon-friUnder the hood, a lightweight CloudFormation stack in your AWS account listens for tag changes via CloudTrail and creates EventBridge Scheduler rules. When a schedule fires, a Lambda function starts or stops the resource directly in your account. Your data never leaves your AWS account.
What you can schedule
| Resource | Action |
|---|---|
| EC2 Instances | Start / Stop |
| RDS Instances | Start / Stop |
| NAT Gateways | Delete / Recreate (with EIP and route preservation) |
| ECS Services | Scale to zero / Restore desired count |
Typical savings
Running a set of dev/staging resources 9 AM–6 PM Monday–Friday instead of 24/7 reduces their uptime from 744 hours/month to roughly 180 hours — a 73% reduction in compute cost for those resources.