07 — AWS Cloud Consulting
AWS architecture, deployment, and a smaller bill
The same stack our own platforms run on. Architecture that fits the workload, and cost optimisation that does not trade away reliability to save a few dollars.
AWS bills grow quietly. An instance sized for a launch that never came, storage nobody has looked at since the migration, data transfer between the wrong two places — none of it announces itself, and all of it renews monthly.
A cost review finds what you are paying for and not using. An architecture review asks a harder question: whether the shape of the system matches what it actually does, which is usually where both the reliability problems and the real savings live.
This comes from running production platforms on the same stack rather than from a certification slide deck. The recommendations are ones we would apply to our own systems.
What you get
Architecture review
Whether the design fits the workload, where it will break under load, and what it would take to fix.
Cost analysis
Where the bill actually goes, which line items are waste, and what each change would genuinely save.
Deployment and infrastructure as code
Repeatable deployments, so environments can be rebuilt rather than nursed.
Security and access review
Over-broad permissions, exposed endpoints and missing guardrails — the findings that matter before they matter.
How it works
Access and context
Read-only access to what exists, and a conversation about what it is supposed to do.
Review and findings
Written, prioritised by impact, with the savings or risk stated plainly rather than implied.
Implement together or alone
We can make the changes, or hand the findings to your team. Either is a fine outcome.
Common questions
Can you reduce my AWS bill?
Usually, though it would be dishonest to promise a figure before seeing the account. The common wins are oversized instances, forgotten storage and avoidable data transfer. What we will not do is trade away reliability for a saving that looks good in a report and hurts in an outage.
Do you need access to my AWS account?
Read-only access is enough for a review, and that is what we ask for. Any change that needs write access is agreed with you first, explicitly and in writing.
Are you AWS certified?
Not currently. The work comes from running production platforms on AWS, and a master’s in Information Technology — AWS Cloud Technologies is in progress rather than complete. We would rather state that plainly than let a logo imply otherwise.
Is this only for large systems?
No. Small accounts often have the highest proportion of waste, because nobody has ever had a reason to look. A short review on a modest bill frequently pays for itself.