Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Fix vpc lattice pattern doc #1914

Merged
merged 1 commit into from
Mar 29, 2024
Merged

docs: Fix vpc lattice pattern doc #1914

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/patterns/vpc-lattice/client-server-communication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
title: Amazon VPC Lattice Client-server Communication
---

{%
include-markdown "../../../patterns/vpc-lattice/client-server-communication/README.md"
%}
2 changes: 1 addition & 1 deletion mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
site_name: Amazon EKS Blueprints for Terraform
docs_dir: docs/
copyright: Copyright © Amazon 2023
copyright: Copyright © Amazon 2024
site_author: AWS
site_url: https://aws-ia.github.io/terraform-aws-eks-blueprints/
repo_name: terraform-aws-eks-blueprints
Expand Down
2 changes: 1 addition & 1 deletion patterns/vpc-lattice/client-server-communication/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This pattern demonstrates how to expose an EKS cluster hosted application to an

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 K8S Gateway API objects. This pattern deploys two distinct VPCs with a client application running in one of them and a server application in the other. The server application is deployed inside an EKS cluster and made exposed to the client application through Amazon VPC Lattice which establishes connectivity between the two applications. Further we demonstrate how to configure a custom domain name for the exposed service using Amazon Route53 and the external-dns project.

![diagram](assets/diagram.png)
![diagram](https://raw.githubusercontent.com/aws-ia/terraform-aws-eks-blueprints/main/patterns/vpc-lattice/client-server-communication/assets/diagram.png)


## Deploy
Expand Down
Loading