From 603e6b9f76a89bfe8b4a75ed92d6078deec4b3d6 Mon Sep 17 00:00:00 2001 From: varunbharill Date: Tue, 16 Nov 2021 14:09:40 -0800 Subject: [PATCH] fix(docs): Add documentation on how to connect to custom ES instance. (#3581) --- docs/deploy/aws.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/deploy/aws.md b/docs/deploy/aws.md index ea0a3b3392..b76034fc3a 100644 --- a/docs/deploy/aws.md +++ b/docs/deploy/aws.md @@ -284,6 +284,15 @@ a different way of creating time based indices. Run `helm upgrade --install datahub datahub/datahub --values values.yaml` to apply the changes. +**Note:** +If you have a custom setup of elastic search cluster and are deploying through docker, you can modify the configurations in datahub to point to the specific ES instance - +1. If you are using `docker quickstart` you can modify the hostname and port of the ES instance in docker compose quickstart files located [here](../../docker/quickstart/). + 1. Once you have modified the quickstart recipes you can run the quickstart command using a specific docker compose file. Sample command for that is - `datahub docker quickstart --quickstart-compose-file docker/quickstart/docker-compose-without-neo4j.quickstart.yml` +2. If you are not using quickstart recipes, you can modify environment variable in GMS to point to the ES instance. The env files for datahub-gms are located [here](../../docker/datahub-gms/env/). + +Further, you can find a list of properties supported to work with a custom ES instance [here](../../metadata-service/factories/src/main/java/com/linkedin/gms/factory/common/ElasticsearchSSLContextFactory.java) and [here](../../metadata-service/factories/src/main/java/com/linkedin/gms/factory/common/RestHighLevelClientFactory.java). + +A mapping between the property name used in the above two files and the name used in docker/env file can be found [here](../../metadata-service/factories/src/main/resources/application.yml). ### Managed Streaming for Apache Kafka (MSK) Provision an MSK cluster that shares the VPC with the kubernetes cluster or has VPC peering set up between the VPC of