towardsthecloud / towardsthecloud/cloudburn
Estimate CloudFront transfer and request costs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Estimate CloudFront data transfer and request costs from explicit monthly traffic assumptions.
Why
A distribution's configuration doesn't reveal how much traffic it will serve. Adding volumes, request counts, and geography gives pull request reviewers a cost estimate they can trace back to inputs they control.
Scope
- Estimate regional data transfer using CloudFront's published tiers
- Price HTTP and HTTPS requests separately
- Respect the distribution's configured price class
- Keep transfer costs unknown when an assumption has no geography
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, tests, or entry points. Start by locating the existing traffic-assumption and cost-estimation code, then trace how distribution price classes and geography are represented. Done means regional transfer tiers, separate HTTP and HTTPS request pricing, configured price classes, and unknown transfer costs for geography-free assumptions are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100