Documentation

Everything you need to set up CloudBurn and get infrastructure cost visibility in your Pull Requests.


Get Cost Visibility Before You Deploy

CloudBurn shows you exactly what your infrastructure changes will cost, directly in your Pull Request. No more surprise AWS bills from that "small change" someone pushed to production.

Here's the setup flow:

Choose Your Path

CloudBurn App

Want cost estimates in your PRs? Start here:

  • Install CloudBurn - Set up the CloudBurn app from GitHub Marketplace to visualize infrastructure costs directly in Pull Requests

GitHub Actions

Already have CloudBurn? These actions generate the diffs and plans that CloudBurn analyzes:

How It Works

  1. You open a PR with infrastructure changes (CDK or Terraform)
  2. GitHub Action runs your CDK diff or Terraform plan
  3. CloudBurn analyzes the output and calculates cost impact
  4. Cost breakdown appears as a comment on your PR

What You'll Find Here

SectionWhat's Covered
InstallPrerequisites, step-by-step setup, permissions, and troubleshooting
Usage ExamplesPractical workflows for single-environment, multi-environment, and reusable patterns
ConfigurationAll available inputs, outputs, and customization options

Quick Start

New to CloudBurn? The fastest path to cost visibility:

  1. Install a GitHub Action first - You need either the CDK Diff Action or Terraform Plan Action to generate infrastructure diffs
  2. Install the CloudBurn App - From the GitHub Marketplace to analyze those diffs and post cost estimates

Already have the GitHub Actions configured? Jump straight to the CloudBurn App installation to add cost analysis to your existing workflow.