Skip to content

SYSTEM Cited by 1 source

Amazon VPC Lattice

Amazon VPC Lattice is AWS's application-networking service positioned as the recommended replacement for customers running AWS App Mesh on EKS / Kubernetes. Architecturally it is not a sidecar service mesh: Lattice provides a managed VPC-level service network, connecting services across accounts, VPCs, and compute substrates (EKS, EC2, Lambda, on-prem via Direct Connect), with routing/auth/observability managed by AWS. No customer-run proxy is required.

Stub page — scoped to the App Mesh discontinuation context. Fill in mechanics on future EKS / VPC-Lattice-focused ingests.

Role in the post-App-Mesh landscape

AWS is splitting the App Mesh replacement story by compute substrate:

  • ECS workloads → Service Connect (sidecar-based, managed Envoy, per-ECS-Service).
  • EKS workloads → VPC Lattice (VPC-level service networking, no sidecars in the Lattice model itself).

This is an architectural bifurcation, not a unification: App Mesh tried to be one mesh across ECS and EKS; Lattice/Service Connect give each substrate a substrate-specific managed alternative.

Why Lattice (not Service Connect) for EKS

Service Connect is ECS-native — it attaches to ECS Services and uses Cloud Map for discovery, neither of which aligns with Kubernetes Services / endpoints / mesh-interface conventions. Lattice operates below the pod/container layer at the VPC networking level, exposing services independently of whether the backend is EKS, ECS, Lambda, EC2, or on-prem.

Seen in

Last updated · 200 distilled / 1,178 read