From 8b0f149882146905afe02695dbbcb7ddcd4b3db8 Mon Sep 17 00:00:00 2001
From: Conor McCullough <103977699+conor-mccullough@users.noreply.github.com>
Date: Wed, 29 Mar 2023 08:41:55 +1100
Subject: [PATCH] Replace broken link (#3119)

Link to the old URL for the dynamic host catalog page removed, added the current valid path.
---
 website/content/docs/troubleshoot/faq.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/troubleshoot/faq.mdx b/website/content/docs/troubleshoot/faq.mdx
index 14e2ffe9d1..33f053a4a4 100644
--- a/website/content/docs/troubleshoot/faq.mdx
+++ b/website/content/docs/troubleshoot/faq.mdx
@@ -37,7 +37,7 @@ from an IDP to Boundary to assign role assignments dynamically. See Boundary's [
 #### Q: Does Boundary automate the discovery and configuration of new targets (e.g. servers)? What happens if a host IP address changes?
 Yes, this is one of the core competencies of Boundary. Boundary can discover new targets in two primary ways
 1. Boundary's [Terraform provider](https://registry.terraform.io/providers/hashicorp/boundary/latest/docs) supports discovery of targets provisioned by Terraform
-2. Boundary's [dynamic host catalog](/boundary/tutorials/oss-access-management/aws-host-catalogs)
+2. Boundary's [dynamic host catalog](/boundary/tutorials/access-management/aws-host-catalogs)
 agentlessly queries infrastructure providers to automate the onboarding and configuration of hosts
 
 All of these methods will automate the discovery and configuration of targets when their ip addresses change. Of course, static hosts can still be manually added via Boundary admin UI and CLI.