--- title: Charmhub | Deploy Opensearch Dashboards using Charmhub - The Open Operator Collection description: Deploy the latest version of Opensearch Dashboards on any cloud. url: https://charmhub.io/opensearch-dashboards/docs/t-deploy --- # Opensearch Dashboards [Canonical](https://charmhub.io/publisher/data-platform "View all packages from Canonical") * [Canonical](https://charmhub.io/publisher/data-platform "View all packages from Canonical") Platform: 24.04 22.04 2/stable 66 ``` juju deploy opensearch-dashboards --channel 2/stable ``` [Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications) --- #### Contacts ##### Maintainers + [Canonical Data Platform Team](mailto:data-platform@lists.launchpad.net) * [Submit a bug](https://github.com/canonical/opensearch-dashboards-operator/issues) --- Share your thoughts on this charm with the community on discourse. [Join the discussion](https://discourse.charmhub.io/) # Get OpenSearch Dashboards up and running The objective of Opensearch Dashboard is to display the contents of an Opensearch database. This is why a functional Opensearch database is a pre-requisite for the Dashboards application to install successfully. So, before going further, let’s set up Charmed Opensearch. Note that Opensearch has a mandatory requirement of TLS support, so we need to deploy it alongside the `self-signed-certificates` charm and integrate (also known as “relate”) them. Make sure that the environment is ready and the Juju model is correctly configured following instructions in OpenSearch Documentation [Set kernel parameters](https://charmhub.io/opensearch/docs/t-set-up#heading--kernel-parameters). Subsequentially we can deploy Opensearch with TLS: ``` juju deploy opensearch --channel=2/edge -n 2 juju deploy self-signed-certificates juju integrate self-signed-certificates opensearch ``` We can simply add the Opensearch Dashboards charm to this setup by deploying and relating it to Opensearch ``` juju deploy opensearch-dashboards --channel=2/edge juju integrate opensearch opensearch-dashboards ``` And there we go! Now if you check the status of your services with `juju status`. Your output should be similar to the example below: ``` Model Controller Cloud/Region Version SLA Timestamp tutorial overlord localhost/localhost 3.5.3 unsupported 16:50:56+02:00 App Version Status Scale Charm Channel Rev Exposed Message opensearch active 2 opensearch 2/edge 159 no opensearch-dashboards active 1 opensearch-dashboards 2/edge 20 no self-signed-certificates active 1 self-signed-certificates latest/stable 155 no Unit Workload Agent Machine Public address Ports Message opensearch-dashboards/0* active idle 3 10.34.169.173 5601/tcp opensearch/0 active idle 0 10.34.169.84 9200/tcp opensearch/1* active idle 1 10.34.169.242 9200/tcp self-signed-certificates/0* active idle 2 10.34.169.5 Machine State Address Inst id Base AZ Message 0 started 10.34.169.84 juju-df6483-0 ubuntu@22.04 Running 1 started 10.34.169.242 juju-df6483-1 ubuntu@22.04 Running 2 started 10.34.169.5 juju-df6483-2 ubuntu@22.04 Running 3 started 10.34.169.173 juju-df6483-3 ubuntu@22.04 Running ``` **Note**: in case you would like to verify the integrations as well, you can add the flag `--relations`. ``` $ juju status --relations ``` Alternatively, if you want to monitor your system (with a view updating every second): ``` $ juju status --watch 1s ``` ---