---
title: "Amazon EKS"
description: "3 posts about Amazon EKS, summarised, each linking to the original."
---

# Amazon EKS
> 3 posts about Amazon EKS, summarised, each linking to the original.

## Articles

### [Scope workloads and share resilience policies with AWS Resilience Hub](https://yomu.fyi/post/scope-workloads-and-share-resilience-policies-with-aws-resilience-hub.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Sinisa Mikasinovic
- Published: Oct 13, 2026
- Type: Tutorial

AWS Resilience Hub’s Next generation, announced September 18, 2026, adds three capabilities to align workload scope and resilience requirements with running environments. Amazon EKS label support selects Kubernetes resources using existing labels with AND logic, establishing precise resource boundaries without reorganizing namespaces. Generative AI-powered Dependency Insights summarizes discovered dependencies and highlights patterns warranting resilience review, such as cross-Region dependencies questioning recovery design. Resilience policy sharing through AWS Organizations lets a central team define requirements once and make them available to member accounts, with policy events tracking adoption. The post walks through scoping a checkout service on EKS using labels, examining dependencies via synthetic traffic, and applying a shared tier-1-critical policy with a 99.9% availability SLO, 5-minute multi-AZ RTO, 1-minute RPO, 15-minute multi-Region RTO, and 60-minute backup intervals.


### [ReadyOn’s Four Walls of tenant isolation on Amazon EKS](https://yomu.fyi/post/readyon-s-four-walls-of-tenant-isolation-on-amazon-eks.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Roshan Daneshvaran
- Published: Sep 18, 2026
- Type: Explainer

ReadyOn describes a four-layer tenant-isolation architecture for Harmony, its multi-tenant workforce-intelligence platform on Amazon EKS, which handles payroll data, organizational hierarchies, and operational analytics. The design combines dedicated Kubernetes namespaces, Karpenter-managed tenant node pools, per-tenant Amazon VPC security groups, and dedicated Amazon Aurora databases, with RBAC, admission control, default-deny network policies, IAM Roles for Service Accounts, and tenant-scoped secrets. GitOps through Argo CD ApplicationSets provisions identical controls and continuously reverts drift, while dual taints and admission validation prevent cross-tenant scheduling. ReadyOn says adversarial exercises have blocked all six tested cross-tenant paths to date, and reports defenses across 10 threat-model stages, though shared control-plane dependencies make the layers defense in depth rather than fully independent probabilities.


### [How Equinix cut operational overhead with a shared services architecture on Amazon EKS](https://yomu.fyi/post/how-equinix-cut-operational-overhead-with-a-shared-services-architectu.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Chhavi Kaushik
- Published: Sep 17, 2026
- Type: Problem & solution

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.