About
I write about cloud engineering in regulated financial institutions — the parts that hyperscaler documentation doesn't cover and FSIs reports get wrong.
I've spent 23 years in enterprise technology across banking and telecommunications. I've led cloud platform organisations of 90+ engineers, architected enterprise landing zones across AWS, Azure, and GCP, and operated platforms where downtime, non-compliance, and ambiguity were not options.
What I cover here spans the full breadth of regulated cloud engineering. Cloud platform patterns and landing zone architecture. IaC governance and multi-cloud strategy. APRA CPS 230, 232, and 243 — not as compliance checklists, but as architecture inputs.Policy-as-code, CSPM, and CNAPP in financial services. FinOps, chargeback models, and the cost governance conversations most cloud teams avoid. SRE, observability, and what operational resilience actually means when you're operating under APRA's 24-hour notification clock.
On the AI side, I cover the full delivery lifecycle — from regulated MLOps and data-to-deployment pipelines through to agentic AI platforms on Azure AI Foundry,Vertex AI, and AWS AgentCore. And the governance layer underneath it all: model risk management, responsible AI, and explainability under APRA obligations.
This blog is for senior cloud engineers, platform architects, and technology executives in financial services who are building or governing cloud platforms in a regulated environment. Not generic AWS tutorials. For people who already know what a landing zone is — and need to know what happens when the regulators ask about it.
I hold AWS and Azure Solutions Architect certifications and an Executive MBA from UNSW. I write here as an independent practitioner.