Skip to content

module.about

I make infrastructure legible.

I work across AWS and Terraform, turning click-ops estates into reviewable infrastructure. Most of my work sits where reliability meets cost: right-sizing what already exists, then making the next change safe to ship.

Region
eu-west-2
Status
available

narrative

I came to cloud engineering the long way round, through support and operations, which is where I learned that most outages are really documentation failures. The estate worked; nobody could say why. That shaped how I build now.

My default is infrastructure as code. If a resource exists, it exists in a repository, with a plan you can read before it lands. Terraform for the estate, pipelines for the path to production, and enough observability that the first person to notice a problem is us rather than a customer.

I care about the unglamorous parts — tagging, cost allocation, least-privilege IAM, the runbook nobody wanted to write. They compound. A year of small, reviewable changes beats one heroic migration.

history

Where I've been, most recent first.

2024 — present

Cloud Engineer

Placeholder Company

AWS estate management, Terraform modules, CI/CD pipelines.

2022 — 2024

Placeholder Role

Placeholder Company

Replace with real position, scope, and one measurable outcome.

2020 — 2022

Placeholder Role

Placeholder Company

Replace with real position, scope, and one measurable outcome.

capabilities

Cloud

  • AWS
  • EC2 · S3 · RDS
  • VPC · Route 53
  • IAM
  • Lambda

Infrastructure as code

  • Terraform
  • CloudFormation
  • Ansible

Delivery

  • GitHub Actions
  • Docker
  • Git

Observability

  • CloudWatch
  • Cost Explorer

Languages

  • Python
  • Bash
  • HCL
  • YAML