Dev Environment Auto-Scheduler
CloudFormation: Lambda and EventBridge rules that stop tagged EC2 and RDS resources outside business hours. Typically saves 65% on dev costs.
Dev Environment Auto-Scheduler
Dev instances running overnight and on weekends are pure waste. This CloudFormation stack deploys Lambda functions and EventBridge schedules that automatically stop tagged EC2 instances and RDS databases outside your configured business hours — and start them back up in the morning. Typical savings: 65% on dev environment costs.
What Is Included
A CloudFormation template that wires up two Lambda functions (stop and start) triggered by EventBridge cron rules. Resources are selected by tag key and value so you can target exactly the right environments. The schedule, timezone, and tag filter are all CloudFormation parameters — no code changes needed.
Developer Experience
- Tag-based targeting — add a tag to opt instances in or out
- Configurable schedule: set your business hours and timezone
- SNS notification on each start/stop cycle (optional)
- One
deploy.shto stand up the whole stack
What You Get
auto-scheduler.yaml— CloudFormation templatedeploy.sh.env.exampleREADME.md
Requirements
AWS account, permissions to deploy CloudFormation (Lambda, EventBridge, IAM roles). EC2 and RDS instances must be tagged with the configured key/value pair.