Context

A fintech company running its platform on AWS, with Kubernetes workloads on Amazon EKS and customers spread across the region. Rahmat joined as a DevOps and infrastructure engineer responsible for the platform end to end.

Challenge

The AWS bill was growing faster than the business, and users far from the hosting region experienced slow API responses. Networking inside the EKS clusters had become complex enough that changes were risky, and infrastructure knowledge sat with too few people.

What Rahmat did

  1. Traced AWS spend to individual workloads and removed or right-sized resources that were idle or oversized.

  2. Planned and led a regional migration that moved services closer to users while live traffic kept flowing, with rollback ready at each step.

  3. Untangled complex Amazon EKS networking issues so that cluster changes became predictable again.

  4. Became the Terraform subject-matter expert for the team, bringing infrastructure under code review and version control.

Results

saved on AWS every month
USD 5,800
lower API latency for regional users
50%
user impact during the region migration
Zero

Stack

  • AWS
  • Amazon EKS
  • Kubernetes
  • Terraform

Let’s talk about your next transformation

Tell me what you are trying to change. I reply personally to partnership and project enquiries.