CloudBoosterDocs
Concepts

ChangeSets

The unit of change in CloudBooster. Every infrastructure change becomes a reviewable, audited ChangeSet in the portal.

ChangeSets

A ChangeSet is what you review and approve in the CloudBooster portal before any AWS resource changes. It is the unit of governance: nothing reaches your AWS account without first becoming a ChangeSet.

Review-gating every change is the point. The ChangeSet is where the human checkpoint lives.

The ChangeSet lifecycle

Blocked is a hold state — the ChangeSet stays here until the approval rules for the target environment are satisfied. From Previewed onward you can re-edit the Composition, which returns the ChangeSet to Previewing.

What you see in the portal

Open a ChangeSet from Projects → Environment → ChangeSets and click a row. The review screen has five tabs:

  • Summary — title, current status, who proposed it, when, and which environment it targets.
  • ADR — the rendered Architecture Decision Record explaining what's changing and why.
  • Diagram — a rendered Mermaid topology of the resulting infrastructure.
  • Composition — the canonical, editable form of the change.
  • Activity — comments, approvals, status transitions, and history.

The Composition tab is where you make edits; the Diagram and Provider plan re-render on Re-preview.

What a ChangeSet contains

You read the ADR and the Diagram. You read or edit the Composition. The Provider plan is what CloudBooster hands to AWS once you approve — it's there for inspection, not for editing.

Where ChangeSets come from

OriginTrigger
Propose a changeYou wrote intent in the portal's intent prompt.
ImportYou're bringing an existing Terraform/Pulumi stack under management.
Portal UIA teammate proposed a change in the web app.
Audit remediationcbx audit aws surfaced a finding you chose to fix.

Every entry point produces the same artifact. Review is the same. Apply is the same.

See also

On this page