Skip to content

Fictional example

Idle staging server needs attention.One decision waits for you.

A sample cloud operations brief: one change tied to its cost, exposure, utilization and customer impact, then one bounded decision.

Acme Orders · AWS · 25 August 2026. Every name and number in this brief is fictional.

What MarshalCloud found

staging-worker-03 looks temporary, but it is still running and exposed to the internet.

The server appeared three days ago after a staging deploy. It barely uses its CPU, has no observed production dependency, and adds to the bill every hour it runs. No customer-facing outage was detected in the same window.

Change

Added 3 days ago

Created by deploy-role in us-east-1

Cost

Projected, not billed yet

Estimate from the current AWS rate and runtime

Security

Public access on

Public IP and SSH open to the internet

Customer impact

None detected

No production dependency or monitor outage found

The proposed action

Awaiting human approval

Stop staging-worker-03.

Stop the verified-idle server. Its disks survive and MarshalCloud can start it again. This removes the runtime cost, but the open firewall rule remains a separate finding until you restrict it.

Risk
Medium · service interruption
Rollback
Supported · start it again
Cost effect
Its running cost stops
Decision
Review before Friday · nothing scheduled
Approve is disabled in this public exampleDismiss or investigate further are also available in-product

Every fix waits for a person: how a fix is drafted and approved

What happens after approval

01

Recheck

Confirm the resource and preconditions still match the reviewed plan.

02

Execute

Run the deterministic, allowlisted provider action, not generated shell code.

03

Verify

Read the provider state back and keep the issue open until it is confirmed.

Expected proof: AWS reports instance i-0a7c3e91 stopped; the action log records approver, executor, result, and time. The separate public-SSH finding stays open rather than being falsely closed. This is an expected outcome, not a claim that this fictional action ran.

What the brief stands on

Evidence coverage

A recommendation is only as current as its slowest relevant source.

AWS inventory

Current

Server state, size, and network path · 9 min ago

AWS change history

Current

Who started it, and when · 6 min ago

AWS usage metrics

Current

CPU and connection utilization · 12 min ago

AWS billing

Delayed

Cost Explorer projection; export pending · 19 hr ago

What is still unknown

The detailed billing export has not arrived, so the cost is a provider-rate projection, not bill-backed realized savings. MarshalCloud should keep that distinction visible.

See this loop with your evidence.

Start read-only, no credit card. Not ready to connect? Run the free bill scan on your own bill.