Identify non-production scheduling candidates
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- aws, typescript
Research direction
Start by reading parent issue #159, then trace the existing handling for AWS resources, beginning with EC2 and RDS. Define how tags, hourly metrics, business hours, weekdays, time zone, utilization thresholds, and minimum savings determine candidates, and verify that Redshift and other safely suspendable services are considered without automatic changes.
Written by the indexing model from the issue text.
Description
What
Identify non-production workloads that are good candidates for scheduled stop and start windows.
Why
Development and test resources often run through nights and weekends despite having predictable business-hour demand. Scheduling can remove a large share of runtime cost, but only when workload intent and usage evidence agree.
Details
- Start with EC2 and RDS, then evaluate Redshift and other services that support safe scheduled suspension.
- Require an explicit non-production signal, such as configured tags, plus a complete hourly utilization lookback.
- Estimate idle off-hours and potential scheduled-hour savings without changing resources automatically.
- Exclude resources with meaningful off-hours activity, high-availability roles, or incomplete metrics.
- Make business hours, weekdays, time zone, utilization threshold, and minimum savings configurable.
Parent: #159
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from towardsthecloud/cloudburn
-
cloudburn-platform enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
towardsthecloud/cloudburn#285 ·
-
cloudburn-platform enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
towardsthecloud/cloudburn#284 ·
-
cloudburn-platform enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
towardsthecloud/cloudburn#283 ·
-
cloudburn-platform enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
towardsthecloud/cloudburn#281 ·
-
cloudburn-platform enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
towardsthecloud/cloudburn#282 ·
All issues in towardsthecloud/cloudburn
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·