Use cases

When the console is not enough

Four moments when teams reach for BunBunCloud.

Incident investigation

Production API latency just went up. Where do you look?

Open the request path: CloudFront, load balancer, target group, ECS service, database. The unhealthy component is highlighted, with the alarm or status behind it, so the first ten minutes go to the right place instead of to console tabs.

  • Health from AWS status, CloudWatch alarms and your probes, every minute
  • What changed recently on the resources in the path
  • Who owns each component, and its monitors and runbooks
Health map for production with resource states
The living architecture diagram

“How does production work?”

A new SRE joins and gets sent Terraform, Confluence pages, old diagrams and Slack threads. Instead, show them the infrastructure that is actually running, and how the components depend on each other, drawn from the accounts themselves.

  • Always current: redrawn after every scan
  • Start from one resource, or show a whole stack
  • Each team sees its own slice first
Architecture diagram of a production load balancer
Environment drift

Staging passed. Production failed.

Staging and production drift apart one console change at a time. See, per resource, which fields differ: engine versions, backup retention, deletion protection, monitoring, Multi-AZ. Accept the differences you intend, and catch the ones you do not.

A database compared across staging and production
AWS spend

“Why did AWS cost more this month?”

See the estimated run-rate of every resource, grouped by service, team, environment or tag, what changed, and which savings are safe to take. Estimates use the public AWS price list, so they work from day one without billing access.

Estimated monthly run-rate and cost by service

Know your AWS infrastructure in 10 minutes

Connect a read-only role. Get the infrastructure report: what you run, what is unhealthy, where environments differ and what it costs. Free, no commitment.