Containers & Serverless on AWS (ECS & EKS)
If your team is still deploying to hand-managed EC2 instances, wrestling with slow Docker builds, or trying to decide whether a workload belongs on containers or serverless, this is where I help. I work with Canada and US teams to modernize how applications get built, packaged, and run on AWS, without a ground-up rewrite. That usually means migrating services to ECS/Fargate or EKS (Kubernetes) — with GitOps via Argo CD and Kustomize and cluster autoscaling where it fits — cleaning up Docker images and build pipelines that have grown slow or redundant, and designing Lambda and API Gateway architectures for workloads that don't need a long-running server at all.
What's included
- ECS/Fargate and EKS (Kubernetes) migrations from EC2 or other hosting
- GitOps delivery with Argo CD and Kustomize, including cluster autoscaling for Kubernetes workloads
- Docker image and build pipeline optimization
- Lambda and API Gateway architecture design for event-driven and serverless workloads
- Right-sizing decisions between containers and serverless based on actual workload shape
- Documentation and knowledge transfer so your team can extend it
Proof it works
- Cut CI/CD build time 60% by switching a React application from build-time to runtime environment variables, eliminating 180 redundant Docker builds.
Is this right for you?
This is a fit if you're running workloads on hand-managed EC2 instances and want to move to a more automated, scalable setup, or if you have workloads that don't need a server running around the clock and could run cheaper and simpler as serverless functions instead. It's also a fit if your Docker build pipeline has grown slow or inconsistent and needs cleanup. Work is scoped and fixed-price, starting with a free 30-minute call to understand your current architecture and what you're trying to achieve — whether that's cost, reliability, deploy speed, or all three. It's not the right fit if you're looking for a full application rewrite or product engineering work — this is infrastructure and deployment architecture, not building product features. Everything delivered, from the container/pipeline configuration to any Lambda architecture, is yours to keep and run independently afterward, backed by documentation and a knowledge-transfer session. I reply to new inquiries within 24 hours and work with teams in Canada and the US.
FAQ
How do you decide between containers and serverless for our workload?
It comes down to the shape of the workload — things like how continuously it runs, its traffic pattern, and cold-start sensitivity all factor in; that's part of what the scoping call and initial review establish rather than a one-size-fits-all default.
How long does a typical migration take?
Typically a couple of days to a couple of weeks, depending on scope, complexity, and how quickly we get access and get oriented in your environment — the scoping call narrows this down before work starts.
Do we need existing Docker/container experience on our team?
No — documentation and knowledge transfer are part of every engagement specifically so your team can operate and extend what's built, regardless of starting experience level.
How it works
Simple, low-friction engagement. No lengthy contracts or discovery phases.
Tell me what you need
Fill out the contact form with a brief description of your challenge. I'll respond within 24 hours.
Quick scoping call
We jump on a 30-minute call to understand your environment, goals, and timeline. I'll follow up with a clear scope and fixed price — usually within a couple of days, up to a week for more complex asks.
I get to work
Hands-on delivery with regular updates. You get clean documentation and knowledge transfer — not a black box.
Done — and you own it
Everything I build is yours. I document it thoroughly so your team can maintain and extend it independently.
Ready to talk about containers & serverless (ecs/fargate & eks)?
Tell me a bit about your challenge and I'll get back to you within 24 hours.
Get in touch →