From c010cdaebbf76f8f9e8eaf27e2805a2ab88fb1e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Allamand?= Date: Fri, 8 Nov 2024 17:10:57 +0000 Subject: [PATCH] add link to blog MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Sébastien Allamand --- patterns/vpc-lattice/cross-cluster-pod-communication/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/patterns/vpc-lattice/cross-cluster-pod-communication/README.md b/patterns/vpc-lattice/cross-cluster-pod-communication/README.md index 5d59ea81e9..e596b912aa 100644 --- a/patterns/vpc-lattice/cross-cluster-pod-communication/README.md +++ b/patterns/vpc-lattice/cross-cluster-pod-communication/README.md @@ -3,6 +3,8 @@ This pattern showcases secure multi-cluster communication between two EKS clusters in different VPCs using VPC Lattice with IAM authorization. It illustrates service discovery and highlights how VPC Lattice facilitates communication between services in EKS clusters with overlapping CIDRs, eliminating the need for networking constructs like private NAT Gateways and Transit Gateways. +> You can also find more informations in the [associated blog post](https://aws.amazon.com/blogs/containers/secure-cross-cluster-communication-in-eks-with-vpc-lattice-and-pod-identity-iam-session-tags/) + ## Scenario With this solution we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native Kubernetes Gateway API objects. This pattern deploys two distinct VPCs each having it's own EKS cluster, which contain an application that will be used to demonstrate cross-cluster communication.