CloudBooster Guard

Terraform PRs + CloudTrail· Read-only

Catch the AWS change before it breaks prod.

Catches risky changes before merge in Terraform PRs, and after the fact in the console, CLI and CI.

One Slack alert within minutes when prod is exposed — who did it, and what it opened.

Setup in about 5 minutes · No credit card

TIDORA

From the team behind TIDORA, an AWS Advanced Tier Services Partner.

01 — Problem

Most risky AWS changes never touch a pull request.

A 30-engineer company running AWS has dozens of ways a dangerous change can land outside Terraform — and outside any review. You own the blast radius of every single one of them.

  1. 01

    Console edits during incidents (ClickOps)

    Someone opens a security group directly in the AWS console to unblock an incident. No PR. No review. No record in your change tracking. You find out when the next incident is already on fire.

  2. 02

    CI jobs changing security groups outside Terraform

    Your deployment pipeline opens a security group inline — it is in a shell script, not a Terraform plan, so your PR linter never sees it. The change is real. The review never happened.

  3. 03

    Terraform module bumps that open SSH to 0.0.0.0/0

    A one-line module version bump. Looks harmless in the diff. Resolved against your live account and org topology, it opens SSH on 12 instances to the internet. The reviewer approved what they could see.

  4. 04

    AI coding agents calling the AWS API

    Coding agents author and apply infra change faster than one person can review. The agent has your repo context. It does not have your account context. That gap is exactly where production breaks.

Production outages from unreviewed infra changes don't arrive gradually. You find out when the page arrives — and spend the next hour reconstructing what happened. Every platform owner has that scar. Guard is built against it.

02 — How it works

One check, two places: every pull request and every AWS account you connect.

Connect your Terraform repos and AWS accounts once. Whether a change arrives as a pull request in any of them, or lands through the console, CLI or a CI script, Guard checks it against your live AWS state and alerts only when production is actually exposed.

Live cloud

Alerts within minutes of the change landing

Reads the CloudTrail log files your trail saves to S3. A Slack alert with the resolved effect: what changed, who changed it, and what is now exposed.

Pull request · optional

Surfaces the danger the diff is hiding

The same check runs on the Terraform plan before apply. One comment on the pull request explains the risk. The status check never blocks a merge on its own.

03 — Why you won't mute us

The second time a tool wastes your attention, you mute it.

So we hold Critical alerts to one danger class and a strict set of conditions.

What Guard catches today

A security-group change that newly exposes a reachable production resource to the public internet on a sensitive port — whether it came from a pull request, the console, the CLI or a CI job.

New danger classes ship only when they meet the same precision bar.

A Critical alert fires only when all conditions hold at once
  • a real transition from not-exposed to exposed
  • a broad internet CIDR (not your office VPN)
  • a sensitive port
  • a reachable resource
  • a production account
  • and not something already baselined as intended
04 — Security

Read-only by default. One IAM role is the only access we get.

The first question every platform owner asks is "why would I let a vendor read my cloud?" Here is what Guard can access, and how that access is limited.

  • One IAM role, read-only

    A single CloudFormation stack creates one cross-account role with read-only permissions. Only CloudBooster's AWS account can use it, and only with your unique External ID. Delete the stack and access ends immediately.

  • Your CloudTrail logs, no AWS Config

    Guard reads the log files your CloudTrail trail saves to S3, and your live configuration through Describe, Get and List calls. No trail yet? One click creates one. It never enables AWS Config. Small AWS cost: about $1 a month per account in S3 request fees.

  • Advisory by default

    The role has no write actions, so by default Guard cannot change your infrastructure. It can change something only if you turn on auto-actions and create a separate write role yourself.

  • GitHub or GitLab: optional, repos you choose

    Pull-request review uses a GitHub App or GitLab integration on the repositories you pick. It posts one comment and a non-blocking status check, and never pushes, approves or merges.

What the read role can doThe full CloudFormation template is published at launch.
Can read
  • Your AWS configuration (AWS-managed ViewOnlyAccess policy)
  • S3 read access, used only for your CloudTrail log files (including encrypted ones)
Limits
  • No write actions of any kind
  • Only CloudBooster's AWS account can use the role, and only with your unique External ID
  • Delete the CloudFormation stack and access ends immediately
05 — Compare

Your PR scanner stays. Guard covers what it can't see.

Most dangerous infra change in a real company does not go through Terraform and a pull request. Guard watches both paths with one check.

Built for

CloudBooster GuardPlatform & infra owners
PR scannersThe PR author
CSPMSecurity teams

Catches changes made outside Terraform (console, CLI, CI)

CloudBooster GuardYes — via CloudTrail
PR scannersNo — sees the diff only
CSPMUsually as a separate runtime / detection product

Reviews pull requests inline

CloudBooster GuardYes
PR scannersYes
CSPMVaries by vendor

Same verdict in the PR and on the live cloud

CloudBooster GuardYes — checked against live account state
PR scannersNo — rules run on code in isolation
CSPMNo — evaluates deployed resources

Fires only on a real not-exposed → exposed transition in prod

CloudBooster GuardYes
PR scannersNo — flags every rule match
CSPMNo — reports a backlog of findings

Pricing model

CloudBooster GuardBy AWS accounts, no seats
PR scannersOpen source, or per developer
CSPMTypically an enterprise contract
Start freeKeep your PR scanner. Add the check it can't run.
06 — Pricing

Priced by cloud accounts, not per seat.

Start free on your prod account. Upgrade when you connect more accounts or need longer history, API tokens or SSO.

Free

Start here
$0

1 cloud account, free forever. Prove it catches something real on prod before you spend a cent.

  • 1 connected cloud account
  • Live change detection
  • PR review on connected repos
  • Slack alerts, with no plan limit on which findings reach Slack
  • 7-day verdict history
  • Not included: API tokens and MCP server
  • Not included: Escalations to your pager or tracker

Starter

$490/mo
Billed monthly

Up to 3 cloud accounts, such as prod, staging and dev. Adds API tokens, the MCP server and escalations.

  • Everything in Free
  • Up to 3 connected cloud accounts
  • 30-day verdict history
  • API tokens: CI uploads plans so repos with remote state get a verdict
  • MCP server: AI agents read your verdicts
  • Escalations of unresolved critical alerts to PagerDuty, Jira, Linear, Microsoft Teams or a webhook
  • Not included: SSO (OIDC) and SCIM provisioning
  • Not included: PR merge holds

Growth

$1,500/mo
Billed monthly

Up to 10 cloud accounts. Adds single sign-on, SCIM provisioning, team views and PR merge holds.

  • Everything in Starter
  • Up to 10 connected cloud accounts
  • 90-day verdict history
  • SSO (OIDC)
  • SCIM provisioning
  • Team views
  • PR merge holds: a risky change waits for review before it merges
  • Not included: Admission and CI apply holds

Scale

Everything in Growth, with a custom number of cloud accounts, 365 days of verdict history, and admission and CI apply holds. Auto-actions are coming soon. We set the account limit with you and quote the price.

Contact sales →

Every plan gets the same detection. Paying more buys accounts, history and integrations — never more noise. Sign up free, then change plan yourself in Settings → Billing.

Prices are in US dollars (USD), billed monthly, excluding VAT. Tax is added at checkout where it applies.

07 — FAQ

The questions every platform owner asks first.

CloudBooster Guard is an AWS change-alerting tool, read-only by default. It checks every infrastructure change — in Terraform pull requests and on the live AWS account via CloudTrail — against your real account state, and alerts in Slack only when a change actually exposes production to the internet.

Built by

Our founders have spent a decade running production AWS.

Guard is built by CloudBooster, founded by the team behind TIDORA, an AWS Advanced Tier Services Partner. Our founders spent a decade as the cloud-engineering function for teams running real, brownfield AWS — Guard is that experience, productized.

Know within minutes when production gets exposed — start free.

No credit card, no agents, no AWS Config — one read-only role from a template you can read first.

  1. Step 1

    Sign up free

    No credit card. One AWS account is free for good.

  2. Step 2

    Launch one CloudFormation stack

    It creates a single read-only IAM role. Review the template in your AWS console before you create it. About five minutes.

  3. Step 3

    Pick a Slack channel

    Alerts go where your team already works. Connect GitHub or GitLab too if you want pull-request review — it's optional.

Review what we can access first →

Need help rolling Guard out across your AWS organization? Implementation support is available through TIDORA, an AWS Advanced Tier Services Partner.