From d0002326060df738e6271d79c739de763da02f71 Mon Sep 17 00:00:00 2001 From: Christina Ausley Date: Fri, 5 Apr 2024 13:56:26 -0400 Subject: [PATCH] a few more links --- .../self-managed/setup/guides/using-existing-elasticsearch.md | 2 +- docs/self-managed/setup/guides/using-existing-opensearch.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/self-managed/setup/guides/using-existing-elasticsearch.md b/docs/self-managed/setup/guides/using-existing-elasticsearch.md index fc4effd2166..6f2be62bc25 100644 --- 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 index 7607c7168fd..204469e3881 100644 --- 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