About the service
I build cloud infrastructure in AWS that handles load, scales with traffic and doesn't silently eat your budget. Over the years I've moved teams from fragile manual setups in the console to a fully declarative approach where every VPC, subnet, security group and IAM policy is described in Terraform, reviewed, versioned and reproduced in minutes. I always start with an audit: map what really works for you today, find single points of failure and places where money leaks, then turn that picture into a clear plan that you approve before a single resource changes.
My everyday work is Kubernetes on EKS, container pipelines and the glue that makes releases boring in the best way. I set up CI/CD so that merging to the main branch goes through autotests, image builds and controlled rollout with health checks and fast rollback, instead of manual deploy on Friday evening. I take observability seriously: plugging in metrics, logs and alerts that report a problem before your customers notice it. Reliability for me isn't a slogan — it's autoscaling to real load, backups that are actually tested for recovery, and infrastructure that survives an entire availability zone going down.
Cost reduction runs through everything I do. I right-size instances, turn off idle resources, tune storage classes and reserved or spot capacity and show you the numbers before and after so savings are measurable, not just talk. You get infrastructure that makes sense to a new engineer from code alone, with documentation and handoff so you don't depend on me.
— AWS architecture: VPC, EKS, RDS, S3, IAM, networking
— Terraform: modules, remote state, reusable code for review
— Kubernetes: EKS clusters, Helm, autoscaling, ingress
— CI/CD with autotests, builds and safe rollouts
— Observability: metrics, centralized logs, alerting
— Audit and continuous cloud cost optimization
My everyday work is Kubernetes on EKS, container pipelines and the glue that makes releases boring in the best way. I set up CI/CD so that merging to the main branch goes through autotests, image builds and controlled rollout with health checks and fast rollback, instead of manual deploy on Friday evening. I take observability seriously: plugging in metrics, logs and alerts that report a problem before your customers notice it. Reliability for me isn't a slogan — it's autoscaling to real load, backups that are actually tested for recovery, and infrastructure that survives an entire availability zone going down.
Cost reduction runs through everything I do. I right-size instances, turn off idle resources, tune storage classes and reserved or spot capacity and show you the numbers before and after so savings are measurable, not just talk. You get infrastructure that makes sense to a new engineer from code alone, with documentation and handoff so you don't depend on me.
— AWS architecture: VPC, EKS, RDS, S3, IAM, networking
— Terraform: modules, remote state, reusable code for review
— Kubernetes: EKS clusters, Helm, autoscaling, ingress
— CI/CD with autotests, builds and safe rollouts
— Observability: metrics, centralized logs, alerting
— Audit and continuous cloud cost optimization
