FINOPS · CLOUD HISTORY
See every change in your cloud, and who made it.
Cloud History reads each cloud's own audit log into one timeline, flags risky changes and changes made outside Terraform, and compares two scans side by side.
FinOps · Cloud History
Cloud History
- 01Changes arrive from every cloud
- 02Each change gets a risk
- 03Filter to what matters
- 04Who, how and from where
- 05Undo, as guidance
- 06Compare two snapshots
- 07See what changed in between
Example data.
How it works
From audit log to answer
Connect your clouds
Read each cloud's own audit log with the required read permission.
Example data.
Every scan saves a snapshot
Each scan records a point-in-time view of the account.
AWS · prod-payments
412 resources
Example data.
Compare any two
Pick two scans of the same account to see what changed between them.
+31 · −6 · 14 modified
Example data.
Timeline
One timeline for four clouds
Cloud History brings each cloud's audit events into one timeline.
| Cloud | Reads | Needs |
|---|---|---|
| AWS | CloudTrail event history | ReadOnlyAccess (LookupEvents) |
| Google Cloud | Cloud Audit Logs | roles/logging.viewer |
| Azure | Activity Log | Monitoring Reader |
| DigitalOcean | Actions API | No actor names |
Changes = write events. Event history adds reads. Live reads now, Stored reads saved events.
One timeline
Waiting for changes
Example data.
Risk
What makes a change risky
Risk follows the event name and payload, from Critical exposure to routine changes; read-only events are never changes.
Authorize
Console · 0.0.0.0/0
Critical
High
Medium
Routine
Example data.
Event details
Every detail, and an honest undo
Open an event to see the details its provider supplied. Zaysa does not run the inverse cloud change for you; you review and apply it yourself.
- Time, actor, identity principal, source IP, tool, region and service.
- Account, event ID, resource, user agent and Raw event.
- Undo the change shows a reversible inverse when one can be described.
- For a Beam access grant, Undo the access can revoke the grant.
AuthorizeSecurityGroupIngress
Raw event ▾
Undo the change reversible
RevokeSecurityGroupIngress
Review and apply it yourself. Zaysa does not run it for you.
Example data.
Snapshots & diff
Snapshots you can compare
Every scan saves a snapshot. Compare two scans of the same account, in older-to-newer order even when you pick them in reverse.
- See added, removed, modified and unchanged resources.
- See the cost change and audit events between scan times.
- No snapshots yet? Run a scan first.
AWS · prod-payments
Pick two snapshots of the same account.
Compared older → newer: Mon → Thu
+31 added
−6 removed
14 modified
392 unchanged
+$842.10/mo
Modified: db-orders · db.r6g.large → db.r6g.xlarge
Audit events between the scans: ModifyDBInstance · user/priya · Console · Wed 16:12
Example data.
INCLUDED IN FREE
Every change, on every plan
Free keeps 30 days of history; Pro and Business keep all of it.
Cloud History
See cloud audit events in one timeline.
Snapshots and diff
Compare scans to see added, removed and modified resources.
Cloud Map
See resources and proven connections.
Waste Cleanup
Review priced waste findings and record cleanup.
Questions
Frequently asked questions
AWS CloudTrail event history, Google Cloud Audit Logs, Azure Monitor Activity Log and DigitalOcean Actions. AWS reads the selected region plus us-east-1 for global services. Google Cloud Admin Activity covers changes; Event history also reads Data Access where supplied.
More in FinOps
See what you run, and what it costs.
Free plan, no card needed.