PR cost estimation puts an AWS cost report on every infrastructure pull request: a commenter action posts your CDK diff or Terraform plan, and the CloudBurn GitHub App replies with the estimated cost change.
Setup steps
From IaC Cost Estimator in your dashboard:
- Install the CloudBurn GitHub App on your GitHub organization. After installation, GitHub sends you back to the dashboard to link it.
- Link the installation to your CloudBurn account. Linking is what licenses PR cost estimations for that organization; after linking you pick a plan and start your 14-day free trial.
- Add the commenter action to CI — aws-cdk-diff-pr-commenter for CDK, or terraform-plan-pr-commenter for Terraform.
- Open a pull request. CloudBurn replies with a cost estimation comment for the changed resources.
How the reports work
The comment contract, report confidence classes (fixed, assumed, unknown), and the .cloudburn/usage-assumptions.json file for usage-based pricing are documented in the GitHub App docs — start with the usage assumptions schema if you want assumption-aware estimates for S3, SQS, and SNS.
Repos, plans, and unlinking
A repository counts as active when it received a cost estimation in the last 30 days, and your plan sets how many active repos you can have — see Plans and billing.
Unlinking an installation stops PR cost estimations for that organization until it is linked again; it does not uninstall the GitHub App from GitHub.
What's next
| Read this | To learn |
|---|---|
| GitHub App overview | How diff comments become cost reports |
| Usage assumptions schema | Pricing usage-billed services from your own numbers |
| Plans and billing | Active-repo limits per plan |