towardsthecloud / towardsthecloud/cloudburn
Choose secure storage for scan results
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Let customers choose where CloudBurn stores their Idle Resources scan results and verify that the selected AWS storage is ready and protected.
Why
Clear storage choices and visible security checks help customers keep control of their data while reducing setup uncertainty.
Scope
- Choose CloudBurn-created storage or an existing dedicated location
- Show the configured location, encryption, retention, and verification state
- Explain failed readiness checks with a clear path to fix them
- Keep scan access limited to the selected customer-controlled location
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 scan-result storage and AWS setup flows, then trace how storage location, encryption, retention, access, and readiness verification are represented. Done means customers can choose a location, see its security state, understand failed checks, and keep access limited to that location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100