towardsthecloud / towardsthecloud/cloudburn
Estimate Amazon RDS gp3 throughput costs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
CloudBurn will include provisioned throughput charges for Amazon RDS gp3 storage when estimating database infrastructure changes.
Why
Throughput above the included baseline can materially change database cost, so surfacing it gives teams a more complete estimate before deployment.
Scope
- Include supported RDS gp3 throughput charges in cost estimates
- Apply the included throughput baseline before calculating additional cost
- Handle equivalent Terraform, CloudFormation, and AWS CDK changes consistently
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 names no files or tests. Start by locating the code paths that estimate RDS gp3 storage changes and their Terraform, CloudFormation, and AWS CDK inputs; trace how equivalent changes reach cost estimates. Done means supported gp3 throughput charges are included only above the included baseline across all three representations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform, typescript
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100