---
title: "How Equinix cut operational overhead with a shared services architecture on Amazon EKS"
description: "Equinix replaced its self-managed Kubernetes environment on Amazon EKS to address operational sprawl caused by independently managed clusters and inconsistent infrastructure practices. The new shared services architecture assigns platform ownership to a cloud operations team while application teams focus on business services. It uses separate Workloads, Platform, and Network accounts: workloads run across two Availability Zones with ALB, Gateway API, Cilium, and Hubble, while shared data services, GitHub Runners, and platform services reside in the Platform account. The Network account provides cross-account and multi-Region connectivity through AWS Transit Gateway, Route 53 Resolver, and Direct Connect. Equinix reports 40% lower operational overhead, 4x higher deployment frequency, and adoption of a unified architecture across multiple business organizations."
---

# How Equinix cut operational overhead with a shared services architecture on Amazon EKS

[AWS](https://yomu.fyi/company/aws) · Chhavi Kaushik · Sep 17, 2026

**Type:** Problem & solution

## Summary

Equinix replaced its self-managed Kubernetes environment on Amazon EKS to address operational sprawl caused by independently managed clusters and inconsistent infrastructure practices. The new shared services architecture assigns platform ownership to a cloud operations team while application teams focus on business services. It uses separate Workloads, Platform, and Network accounts: workloads run across two Availability Zones with ALB, Gateway API, Cilium, and Hubble, while shared data services, GitHub Runners, and platform services reside in the Platform account. The Network account provides cross-account and multi-Region connectivity through AWS Transit Gateway, Route 53 Resolver, and Direct Connect. Equinix reports 40% lower operational overhead, 4x higher deployment frequency, and adoption of a unified architecture across multiple business organizations.

## Context

Equinix’s earlier model gave individual application teams responsibility for provisioning and operating separate self-managed Kubernetes clusters. The resulting duplication, inconsistent governance, independently implemented shared services, and recurring cluster lifecycle work made the environment difficult to manage, secure, and scale.

## Approach / What changed

Equinix migrated to a multi-account Amazon EKS design with separate Workloads, Platform, and Network accounts. The cloud operations team centrally manages shared data services, GitHub Runners, networking, and governance, while application workloads use dedicated namespaces, Cilium network policies, Hubble observability, ALB and Gateway API ingress, and controlled connectivity through AWS Transit Gateway, Route 53 Resolver, and Direct Connect.

## Takeaways

- The Platform account centralizes Amazon RDS, Amazon MSK, Amazon OpenSearch Service, Amazon MQ, Amazon S3, GitHub Runners, and other shared services for application teams.
- Cilium provides pod-level network isolation and Hubble supplies unified network-flow visibility across the Workloads and Platform environments.
- The migration is reported to have reduced operational overhead by 40%, increased deployment frequency fourfold, and enabled onboarding in days rather than weeks.

## FAQ

### How are workloads separated from shared platform services?

Application workloads run in the Workloads account, while shared infrastructure services run in the separately owned Platform account. Cross-account communication is controlled through AWS Transit Gateway attachments, and Cilium network policies provide pod-level isolation.

### What networking connects the accounts and regions?

A dedicated Network account acts as the connectivity hub. AWS Transit Gateway spans us-west-1 and us-east-2 with peering between regions, while Route 53 Resolver supports DNS resolution and AWS Direct Connect provides hybrid connectivity to on-premises Equinix routers.

### What operational results did the migration deliver?

Equinix reports a 40% reduction in operational overhead and a 4x increase in deployment frequency. It also reports a unified architecture across multiple business organizations and onboarding in days instead of weeks.

**Tags:** [Amazon EKS](https://yomu.fyi/topic/amazon-eks), [Architecture](https://yomu.fyi/topic/architecture), [Cilium](https://yomu.fyi/topic/cilium), [Kubernetes](https://yomu.fyi/topic/kubernetes)

- Source: [AWS](https://aws.amazon.com/blogs/architecture/how-equinix-cut-operational-overhead-with-a-shared-services-architecture-on-amazon-eks)
- Source URL: https://aws.amazon.com/blogs/architecture/how-equinix-cut-operational-overhead-with-a-shared-services-architecture-on-amazon-eks
- Ingested by Yomu: 2026-09-17T18:04:36.523Z

[Read original post](https://aws.amazon.com/blogs/architecture/how-equinix-cut-operational-overhead-with-a-shared-services-architecture-on-amazon-eks)