EC2 and unattached EBS
Inventory and utilization context support idle-instance and detached-volume review.
SpendLens
AWS cost forensics for engineering-led startups.
Read-only AWS analysis brings customer-owned CUR data and inventory context into findings your team can review.
What it does
Evidence for the review, not a black box.
S3 lifecycle signals
Lifecycle signals are surfaced alongside relevant context.
RDS rightsizing
RDS context supports a rightsizing review.
How you start
Connect context in three steps.
- Create a cross-account read-only role with an external ID.
- Connect the customer-owned CUR export.
- Review scan results and attached evidence.
Walkthrough
See the evidence before the decision.
app.probackend.com/spendlens/reports · synthetic reference sample
Unattached EBS volume
HIGH · review needed
Resource context · age · size · estimated savings field
# remediation draft aws ec2 delete-volume --volume-id <volume-id>
Read-only access
The customer keeps resource control
Remediation remains human-applied guidance
Fit
Who it is for.
- Engineering teams needing evidence for spend review.
Not for
Where it does not fit.
- Bill payment tools.
- Infrastructure mutators.
FAQ
Questions before you start.
Does SpendLens need AWS keys?
No. The documented model uses a cross-account read-only role protected by an external ID.
How is the role protected?
The customer creates a cross-account read-only role with an external ID.
Who owns the CUR export?
The customer-owned CUR export remains the customer’s data context.
What does a finding contain?
Findings attach severity, resource context, an estimated-savings field, evidence, and remediation guidance where available.
Can SpendLens apply remediation?
No. Remediation remains customer-applied guidance.
What detector coverage is described here?
This page describes EC2 idle signals, unattached EBS, S3 lifecycle signals, and RDS rightsizing review only.