How To: Connect Bitbucket Data Center hosted on Kubernetes to AWS OpenSearch service
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This page describes how to connect the AWS OpenSearch service to our Bitbucket installation on Kubernetes.
Environment
Bitbucket Data CenterKubernetes
Solution
Set the below values for OpenSearch in the values.yaml
file:
1
2
3
4
5
6
7
opensearch:
install: false
baseUrl: https://search-ajaitly-opensearch-url-XXXXXXX.us-west-2.es.amazonaws.com
credentials:
secretName: search-credentials
usernameSecretKey: username
passwordSecretKey: password
Ensure that you have clustering set to true:
1
2
3
4
5
6
clustering:
# -- Set to 'true' if Data Center clustering should be enabled
# This will automatically configure cluster peer discovery between cluster nodes.
#
enabled: true
The Bitbucket UI on the Administration page will show the below:

Confirm by logging into the Bitbucket Pod, that the bundled search process isn't running. You'll only see Bitbucket and Mesh process when you run the command "ps -ef | grep java
". There wouldn't be any OpenSearch Pod created in your Kubernetes cluster either.
Was this helpful?