towardsthecloud / towardsthecloud/cloudburn
Store optimization scan results securely in customer accounts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Store Cost Optimization scan results in the customer’s own AWS account using a consistent snapshot format for the overview and every optimization area.
CloudBurn will keep only the information needed to locate and authorize each scan, while full findings remain customer-owned.
Why
This preserves CloudBurn’s strong data boundary while enabling reliable history, filtering, and focused review experiences.
Scope
- Keep full findings in customer-owned storage
- Publish each completed scan as one consistent snapshot
- Preserve the previous successful snapshot until a replacement is ready
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
No files, tests, or entry points are named. Start by locating the Cost Optimization scan completion and persistence paths, then determine how customer-owned AWS storage and scan authorization should be represented. Done means full findings remain in the customer account, each completed scan is one consistent snapshot, and the previous successful snapshot survives until replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100