towardsthecloud / towardsthecloud/cloudburn

Recommend EBS Snapshot Archive for cold snapshots

Open
#175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
1.8k
Forks
371
Avg merge
4h 32m
Merged PRs (30d)
63

Description

What

Recommend EBS Snapshot Archive for large, cold snapshots whose retention pattern fits the archive tier.

Why

Long-retained snapshots that are rarely restored can cost less in the archive tier, but archive minimum duration and restore charges make age alone an unsafe recommendation.

Details

  • Research the reliable evidence available for snapshot restore frequency and archive eligibility.
  • Require a completed snapshot, a configurable age and size floor, no recent restore signal, and expected retention beyond the archive minimum.
  • Compare estimated standard snapshot storage cost with archive storage and likely restore cost.
  • Include retention assumptions and break-even period in the finding so users can review the tradeoff.
  • Discovery only. Keep this separate from Fast Snapshot Restore work in #119.

Parent: #159

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by researching reliable evidence for EBS snapshot restore frequency, archive eligibility, minimum duration, and restore charges. Define the discovery finding's configurable age and size thresholds, retention assumptions, recent-restore signal, and standard-versus-archive break-even comparison; done when the recommendation clearly exposes those tradeoffs without covering Fast Snapshot Restore work.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.