Open Source / Open-source tool
EC2 Reaper
Tag-driven schedules that stop paying for non-production compute outside working hours.
The work
The challenge
Development and staging resources can stay billed around the clock even when nobody uses them.
The approach
Use explicit tags and schedules to identify eligible non-production resources. Working-hour start and stop behavior is part of the schedule.
Implementation
A Lambda and Terraform automation package is linked with a full journal walkthrough. Review exclusions and operational requirements before enabling a schedule.
Context & results
A public automation tool, not a client savings claim. Benefits depend on the resources, runtime schedule, and account pricing.