/ AWS audit · fixed price · read-only
AWS audit at a fixed price.
Find what is idle, what is exposed and what is not in code, before it shows up on your bill, in a customer’s security questionnaire or in front of an auditor. Read-only access, a written report in 5-7 working days.
- Read-only IAM role, you review the policy first
- Nothing in your account is changed
- Findings come with evidence, not verdicts
01 Access
Why it is safe to let us in.
You write the door
You create a read-only IAM role from a policy you can read and review before anything happens.
Read-only by design
The audit tool, InfraLens, makes read calls only. This is enforced in code and covered by tests. Open source, Apache-2.0: you can read it.
You close the door
When the report is delivered, you delete the role. Nothing stays behind.
02 Scope
Four layers, joined into one picture.
Most audits hand you four separate lists. This one connects them: what exists, what it costs, what looks exposed, and whether it is under code.
Cost
Where the bill really goes, taken from billing data, not a price list. Idle and orphaned resources with their monthly cost.
Security
Public exposure, root and IAM hygiene, logging gaps, mapped against what AWS itself already reports.
Infrastructure as code
What is in Terraform or CloudFormation, what is not, and where the two have drifted apart.
Blast radius
What depends on what, so you know what to check before anything is removed.
03 Deliverable
A document you can hand to your board, customer or auditor.
The report is written for a decision-maker, not only for engineers, in plain language, ordered by severity, then by money at stake, then by how cheap the fix is.
- Summary with the numbers that matter
- Ordered action list: what to do first
- Each finding with its evidence and confidence
- An explicit list of what was not checked
04 Process
From first call to report in 5-7 working days.
20-minute call
Scope, accounts, what worries you. No slides.
Access
You create the read-only role from the policy we send.
Scan and analysis
Automated scan, then manual review of what the tool cannot judge.
Report and walkthrough
Written report and a call to go through it with your team.
05 Offer
Fixed price, no surprises.
| Snapshot · start here | Full audit | Audit + fix | |
|---|---|---|---|
| AWS accounts | 1 | up to 3 | up to 3 |
| Scan and top findings | ✓ | ✓ | ✓ |
| Client-ready report by area | — | ✓ | ✓ |
| Cleanup scripts and roadmap | — | ✓ | ✓ |
| Implementation of fixes | — | — | ✓ |
| Price | €900 | €2,400 | from €4,500 |
Prices exclude VAT. Not sure which fits? Start with a Snapshot: it is a complete scan of one account and the cheapest way to see what is there.
This month: 3 free pilot audits in exchange for a short testimonial and an anonymised case study.
06 Who is behind this
Vakhtang Mosidze. In IT since 1996.
I started in 1996 as the IT person at a hospital, then ran IT at an airline, built a cybersecurity company for banks and oil and gas, and went on to CTO and head of DevOps roles. I have built a 1,500-node compute cluster and moved production to Kubernetes. Physicist by training. These days I help European teams see what is really running in their infrastructure, and keep it under control. Based in Tallinn.
I wrote the tool I use for these audits and a book about the on-premise Kubernetes work behind them.
Want to know what is in your AWS account?
Twenty minutes, no slides, no obligation.