Project

Migration to Amazon EKS

Migration of a backend infrastructure from EC2 to Amazon EKS, achieving zero downtime, automated deployments, and scalable, observable workloads to support seasonal traffic surges.

Overview

To address deployment inconsistency, limited autoscaling, and traffic-related performance issues, I led the transition from EC2-based hosting to a fully containerized and orchestrated infrastructure on Amazon EKS. This migration was mission-critical, with requirements for zero downtime, improved performance, and a smoother developer experience across testing, staging and production environments.

Technical details

The migration project was delivered in structured phases: containerization, Helm-based standardization, infrastructure provisioning, CI/CD pipeline automation, observability instrumentation, and team onboarding. It combined Kubernetes operational best practices with a strong focus on reliability and enablement.

  • Infrastructure: Amazon EKS, Managed Node Groups, VPC, Private Subnets, IAM Roles
  • Containerization: Docker, Helm, Kubernetes
  • CI/CD: GitHub Actions, Amazon CodePipeline
  • Secrets Management: AWS Secrets Manager
  • Observability: DataDog (metrics, dashboards, probes, alerts)
  • App Stack: Python APIs, NodeJS apps
  • Orchestration Features: HPA, readiness/liveness probes, resource limits

Challenges

  • Zero-downtime migration of production traffic with minimal rollback windows
  • Coordinating deployment strategy across multiple services and teams
  • Educating engineering teams on Kubernetes operations and container-native practices
  • Ensuring security and observability from the outset
  • Achieving efficient autoscaling for unpredictable seasonal traffic spikes

What changed.

  • 100% production workload migrated with zero service interruption
  • 60% faster deployment cycles and reduced release-related errors
  • 2x increase in traffic successfully absorbed with no performance bottlenecks
  • Standardized deployment processes led to fewer hotfixes and greater developer confidence
  • Infrastructure cost stabilized, thanks to better resource allocation and idle resource trimming
  • Strengthened DevOps culture across the engineering team through documentation and working sessions

Want to talk about your product?

If you're setting up the foundations for your product and your team, let's have a 20-minute chat.

Book a 20-minute chat