Freelance AWS consultant
Most of the last decade of my work has been on AWS — for an online bank, an international leasing company and a manufacturing marketplace. What follows is the work I actually get called in for.
Scope
What I take on
Account and network layout
Multi-account structure, VPC and subnet design, segmentation, and the boring guardrails that stop an estate sprawling — so the thing is still comprehensible in two years.
Workloads
ECS and EC2, RDS, S3, DynamoDB, API Gateway, CloudFront. Sizing, placement, autoscaling and the failure modes each one actually has.
Migration off legacy
Moving estates from on-prem, from a single monolithic environment, or from a hosted provider onto AWS — in stages, with production running the whole time.
Cost and availability
Finding where money is being burned on idle capacity, and where a single point of failure is quietly waiting for a bad Tuesday.
Method
How it runs
-
01
Read the estate first
Before anything moves, I map what is really running, what depends on what, and which parts nobody dares touch. Migration plans built from the architecture diagram rather than from reality are how weekends get ruined.
-
02
Codify, then cut over
The target gets built in Terraform before traffic goes anywhere near it. That makes the cutover reversible, and it means you are left with infrastructure your team can rebuild rather than a hand-made environment nobody understands.
-
03
One environment at a time
Staged migrations with a real rollback path. I have never needed a big-bang weekend cutover and would push back hard on one.
Evidence
Where this has been done before
- 3D Hubs Redesigned a monolithic infrastructure into isolated, reproducible environments on AWS with Terraform, so scaling and testing stopped fighting each other.
- LeasePlan Ran SAP OpenText hosting on AWS where high availability was the hard requirement, and automated the instance configuration that had been manual.
- Knab AWS work inside a regulated Dutch bank — ECS, RDS, CloudFront, API Gateway and DynamoDB, under the evidence requirements that come with financial services.
Fit
Probably worth a conversation if
- You are on AWS already but it grew by hand and nobody can reproduce it.
- You are planning a migration and want someone who has done staged cutovers before.
- Your bill or your availability is telling you the architecture needs a rethink.
- You need AWS depth for a fixed period without hiring a permanent engineer.
Contact
Tell me what is actually broken
The contact details live on the front page. If I am not the right person for this, I will say so.