towardsthecloud / towardsthecloud/cloudburn
Estimate Auto Scaling group capacity 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 estimate the cost impact of Auto Scaling group desired capacity, including changes to the number and type of instances in a group.
Why
Teams can see how scaling decisions affect expected AWS costs before applying an infrastructure change.
Scope
- Price desired-capacity changes for supported Auto Scaling groups
- Handle equivalent Terraform, CloudFormation, and AWS CDK changes consistently
- Report mixed or incomplete instance configurations without inventing a price
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 in the issue. Start by locating the existing pricing and infrastructure-change handling for Terraform, CloudFormation, and AWS CDK, then trace how Auto Scaling group configurations are represented. Done means consistent desired-capacity cost estimates across the supported formats, with mixed or incomplete instance configurations reported without a fabricated price.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100