fix: Link to vpc lattice doc (#1986)

Signed-off-by: Sébastien Allamand <[email protected]>
aws-ia · Jul 31, 2024 · afd006d · afd006d
1 parent c299452
commit afd006d
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 3 deletions.
diff --git a/docs/patterns/vpc-lattice.md b/docs/patterns/vpc-lattice.md
@@ -1,5 +1,5 @@
 ---
-title: Amazon VPC Lattice
+title: VPC lattice
 ---
 
 {%

diff --git a/docs/patterns/vpc-lattice/cross-cluster-pod-communication.md b/docs/patterns/vpc-lattice/cross-cluster-pod-communication.md
@@ -0,0 +1,7 @@
+---
+title: Cross VPC and EKS clusters secure Communication
+---
+
+{%
+ include-markdown "../../../patterns/vpc-lattice/cross-cluster-pod-communication/README.md"
+%}
diff --git a/patterns/vpc-lattice/README.md b/patterns/vpc-lattice/README.md
@@ -5,9 +5,9 @@ This folder contains use case-driven patterns covering different aspects of the
 ## Use cases
 
 - [Simple Client to Server Communication](./client-server-communication/)
- - This pattern describes how to expose a simple API within an Amazon EKS cluster deployed in VPC A to a client application hosted in VPC B through Amazon VPC Lattice.
+  - This pattern describes how to expose a simple API within an Amazon EKS cluster deployed in VPC A to a client application hosted in VPC B through Amazon VPC Lattice.
 - [Cross VPC and EKS clusters secure Communication](./cross-cluster-pod-communication/)
- - This patterns shows how to make 2 services in 2 different EKS clusters and VPC can communicate securely on private domain and sigV4 authorization.
+  - This patterns shows how to make 2 services in 2 different EKS clusters and VPC can communicate securely on private domain and sigV4 authorization.
 
 
 ## Supporting resources