towardsthecloud / towardsthecloud/cloudburn
Configure Idle Resources checks and exceptions
Open
Nobody has claimed this yet.
cloudburn-platform
enhancement
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Let customers choose which Idle Resources checks run for each AWS account and configure tag-based exceptions and report context.
Why
Account-specific controls reduce noise while keeping each scan explainable and aligned with the team's ownership conventions.
Scope
- Set defaults for new accounts and overrides for individual accounts
- Enable or disable checks by category
- Suppress findings with approved exception tag keys
- Include a limited set of chosen tag keys in reports
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.
Research direction
The issue does not name files or tests. Start by locating the Idle Resources checks and the account configuration and reporting entry points; map how defaults and account overrides are represented. Done means checks can be enabled or disabled per category, approved tag exceptions suppress findings, and selected tag keys appear in reports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100