Add Savings Plans coverage guardrail rules
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- aws, typescript
Research direction
Start in the costguardrails module and inspect the account-level dataset pattern used by costguardrails and costexplorer, including how rules declare discovery dependencies and the SDK owns loaders. Review the Savings Plans API and Cost Explorer coverage endpoints first. Done means cross-service discovery rules cover compute spend with no active plans and plans nearing expiry, following the CLDBRN-AWS-COSTGUARDRAILS-N sequence.
Written by the indexing model from the issue text.
Description
What
Discovery rules in the costguardrails module that flag accounts with compute spend but no active Savings Plans, and Savings Plans nearing expiry.
Why
CloudBurn covers Reserved Instance coverage per service (CLDBRN-AWS-EC2-7 and -12, CLDBRN-AWS-RDS-3, CLDBRN-AWS-ELASTICACHE-1, and CLDBRN-AWS-REDSHIFT-2) but lacks general Savings Plans lifecycle guardrails. Savings Plans are the commitment model AWS steers customers toward for EC2, Fargate, and Lambda.
Details
- Candidate rules: sustained compute spend with zero active Savings Plans; Savings Plans expiring within a review window; optionally, low Savings Plans utilization.
- Data comes from the Savings Plans API and Cost Explorer coverage endpoints, following the account-level dataset pattern used by
costguardrailsandcostexplorer. - Discovery only. Continue the
CLDBRN-AWS-COSTGUARDRAILS-Nsequence per the contiguous-ID convention. - Follow the dataset-driven model: rules declare discovery dependencies and the SDK owns loaders.
- PR #207 implements the SageMaker-specific low-coverage slice as
CLDBRN-AWS-SAGEMAKER-3. This issue remains open for the cross-service lifecycle guardrails above.
- 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 ·