a few more links

camunda · Apr 5, 2024 · d000232 · d000232
1 parent 1c75a05
commit d000232
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/self-managed/setup/guides/using-existing-elasticsearch.md b/docs/self-managed/setup/guides/using-existing-elasticsearch.md
@@ -102,7 +102,7 @@ elasticsearch:
 
 ## Next steps
 
-Use the custom values file to [deploy Camunda 8](../deploy.md) as usual:
+Use the custom values file to [deploy Camunda 8](/self-managed/setup/overview.md) as usual:
 
 ```sh
 helm install camunda camunda/camunda-platform -f existing-elasticsearch-values.yaml

diff --git a/docs/self-managed/setup/guides/using-existing-opensearch.md b/docs/self-managed/setup/guides/using-existing-opensearch.md
@@ -6,7 +6,7 @@ description: "Learn how to use an AWS managed OpenSearch instance in Camunda 8 S
 
 Camunda 8 Self-Managed has two different types of components: Camunda components (Operate, Optimize, Tasklist, etc.) and non-Camunda dependency components (such as Keycloak and Elasticsearch). For more details, review the [architecture](/self-managed/platform-architecture/overview.md) documentation for more information on the different types of applications.
 
-This guide steps through using an existing AWS managed OpenSearch instance. By default, [Helm chart deployment](../deploy.md) creates a new Elasticsearch instance, but it's possible to use AWS managed OpenSearch instead.
+This guide steps through using an existing AWS managed OpenSearch instance. By default, [Helm chart deployment](/self-managed/setup/overview.md) creates a new Elasticsearch instance, but it's possible to use AWS managed OpenSearch instead.
 
 ## Preparation
 
@@ -64,7 +64,7 @@ global:
 
 ## Next steps
 
-Use the custom values file to [deploy Camunda 8](../deploy.md) as usual:
+Use the custom values file to [deploy Camunda 8](/self-managed/setup/overview.md) as usual:
 
 ```sh
 helm install camunda camunda/camunda-platform -f existing-elasticsearch-values.yaml