Connecting is read-only. Fixes need a second role you choose to install (the AWS setup guide). For now we switch fixes on with you: you install the fix role in your AWS account and we record it on your connection. A screen to do it yourself is coming.
Screens are from a sample workspace with seeded data, not a customer's.
How does an approval-gated fix work?
MarshalCloud drafts the change but cannot run it. The plan names the resource, the dollar impact and whether it can be undone, then waits for a person.
Propose, approve, execute
Propose, then a person approves, then it executes.
Propose
Drafts the exact change, priced from your bill, says whether it can be undone, then stops.
Approve
A person with approval rights approves that one action. Both names are recorded.
Waiting for you
Execute
Rechecks live state, makes the one approved change, records every step.
Irreversible actions never run without a person. One exception exists: a server stop schedule a person already approved.
Every action carries its own undo story.
Every plan ends with one of these three sentences, before you approve it.
Reversible
“You can undo this with one click.”
A rollback restores the same resource: a stopped server, a changed disk type, a resized instance.
Compensating
“Undo recreates an equivalent - the original is gone.”
Undo builds a new disk from the 14-day safety snapshot, and only while that snapshot lives.
Irreversible
“This cannot be undone.”
Releasing an IP address, deleting a backup or buying a savings plan. Each needs an extra confirmation.
What can it fix today?
A fixed set of AWS changes across cost, security and commitments, a few of them below. Nothing outside the set can be proposed or run, and the fix role you install allows only those.
