Best Practices on Setting up Multi Cluster Service Mesh in AWS
summary
Shows a concrete build on EKS and Istio that achieves cross-cluster mTLS and service discovery using EKS + Istio mTLS, with a centralized AWS PCA issuing mesh CAs and private keys stored in AWS PCA + Secrets Manager for Day‑0 and Day‑2 rotation. Uses cross‑account RAM/IAM to mint intermediates, exchanges remote kubeconfig secrets with long‑lived tokens for discovery, and connects clusters over Transit Gateway to an NLB east‑west gateway using NLB East‑West SNI passthrough (port 15443). Includes terraform/Backstage templates for reproducible deployment.
AI-written summary · about
related talks
50mMulti-Cluster Kubernetes and Service Mesh Patterns
27mBridging Trust Between Multi-Cluster Meshes
25mAdministering Multi Cluster Service Meshes Securely
01h 11mMulti-cluster Service Mesh Workshop
32mMulti Cluster and Multi Mesh Patterns
41mService Mesh beyond single clusters
11mLightning Talk: Multi-cluster Istio Mesh – Complex or Piece of Cake?
36mBuilding a Multi Cluster/Env Service Mesh at Airbnb
