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.

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

fix broken links #143

Merged
merged 1 commit into from
Mar 21, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 4 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,7 @@
scripts/aws_sdk_model_override/aws-sdk-go
coverage.out
deploy.yaml

# MkDocs documentation
site*/

2 changes: 1 addition & 1 deletion docs/configure/index.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# Configure AWS Gateway API Controller
Refer to this document to further configure your use of the AWS Gateway API Controller.
The features here build on the examples shown in [Get Started Using the AWS Gateway API Controller](getstarted.md).
The features here build on the examples shown in [Get Started Using the AWS Gateway API Controller](../getstarted.md).
2 changes: 1 addition & 1 deletion docs/getstarted.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Get Start Using the AWS Gateway API Controller

Once you have [deployed the AWS Gateway API Controller](configure.md), this guide helps you get started using the controller.
Once you have [deployed the AWS Gateway API Controller](configure/index.md), this guide helps you get started using the controller.

The first part of this section provides an example of setting up of service-to-service communications on a single cluster.
The second section extends that example by creating another inventory service on a second cluster on a different VPC, and spreading traffic to that service across the two clusters and VPCs.
Expand Down