Problem
Kubernetes services and workloads were communicating across availability zones and regions more often than needed, increasing AWS transfer spend.
Cut Inter-AZ and Cross-Region Traffic Costs by up to $25K per Month
AWS EKS clusters were generating expensive inter-AZ and cross-region data transfer charges. I analyzed service communication paths, workload placement, and traffic behavior to identify where network cost was being created unnecessarily.
Action
Investigated EKS traffic flows, optimized workload placement and service communication patterns, and reduced unnecessary cross-zone and cross-region paths.
Impact
Reduced AWS data transfer costs by up to $25K per month while keeping reliability and production traffic requirements in view.
- Reduced inter-AZ and cross-region AWS data transfer charges
- Improved visibility into EKS network cost drivers
- Optimized Kubernetes service and workload communication
- Balanced cost savings with reliability and traffic locality