Cloud infrastructure should be two things: secure and boring. If your AWS account is a pile of hand-clicked resources nobody fully understands, or your bill keeps growing for reasons nobody can explain, that’s fixable.
I design, migrate, and run AWS infrastructure for a living, including multi-account organizations that pass real security review.
Services
What I do on AWS
- Cloud migration, including zero-downtime cutovers for production workloads
- Architecture design and review: VPCs, ECS and Fargate, Lambda, RDS and Aurora, CloudFront
- Cost optimization: finding and cutting the waste most AWS accounts quietly accumulate
- Serverless builds with Lambda, AWS SAM, and the Serverless Framework
- Multi-account organizations with security baselines: CloudTrail, GuardDuty, Config
Proof it works
Production results, not slideware
HIPAA migrations
Zero-downtime, HIPAA-compliant migrations for healthcare workloads.
$500M a year
I operate the AWS footprint behind a travel platform processing over $500M annually.
Terraform always
Every resource is code: reviewed as a plan, version controlled, reproducible.
Infrastructure as code, always
Every resource I provision is defined in Terraform or an equivalent tool, reviewed as a plan before it applies, and version controlled. Nothing lives only in the console. That means your infrastructure is reproducible, auditable, and doesn’t depend on anyone’s memory, including mine.
The same discipline applies whether your bill is five hundred dollars a month or fifty thousand.
Talk through your AWS setup
A short call is usually enough to tell you what a migration or cleanup would take.