VPC Lattice quietly became the easiest way to connect services across accounts

Before VPC Lattice, connecting services across multiple AWS accounts meant wrestling with VPC peering, Transit Gateways, PrivateLink endpoints, and mountains of IAM policies. Each approach had trade-offs in cost, complexity, and blast radius.

VPC Lattice flips the model: you define a "service network" and attach services to it. Any VPC associated with that network can reach those services — no route tables, no peering connections, no NAT gateways in the path.

The real magic is the auth policies. You can write IAM-style conditions like "only allow requests from account 123456 signed by role X." It's service mesh semantics without the sidecar complexity. And because it operates at the hypervisor level, there's no extra hop — latency stays flat.