Verify that OpenSearch is responding

curl -k -u admin:<PASSWORD> https://<IP_DE_LA_VM>:30920/

‍

Expected output

{
  "name": "opensearch-node",
  "cluster_name": "...",
  "version": { "number": "2.x.x" }
}

‍

Cluster status

curl -k -u admin:<PASSWORD> https://<IP_DE_LA_VM>:30920/_cluster/health?pretty

‍

ℹ️ OpenSearch uses HTTPS with self-signed certificates. Use `-k` in curl or configure your client to accept self-signed certificates. If you didn't set a password during deployment, look for it in the deployment outputs in the Cuemby portal.

# View the OpenSearch pod
`kubectl get pods -A | grep opensearch`

# View the installation log
`tail -f /var/log/cuemby/bootstrap.log`

‍

Expected output

NAME                           READY   STATUS    RESTARTS
opensearch-xxxxxxxxx-xxxxx     1/1     Running   0        ← Running ✓

‍

⚠️ OpenSearch may take 5–8 minutes to become available. It is a large application that initializes system indexes on first boot.

Create an index

curl -k -u admin:<PASSWORD> -X PUT https://<IP_DE_LA_VM>:30920/mi-indice \
  -H "Content-Type: application/json" \
  -d '{"settings": {"number_of_shards": 1, "number_of_replicas": 0}}'

‍

Index a document

curl -k -u admin:<PASSWORD> -X POST https://<VM_IP>:30920/my-index/_doc

-H "Content-Type: application/json"

-d '{"title": "OpenSearch on Cuemby", "content": "Distributed Search Engine"}'

‍

Search for documents

curl -k -u admin:<PASSWORD> -X GET https://<VM_IP>:30920/my-indice/_search?pretty \ 
-H "Content-Type: application/json" \ 
-d '{"query": {"match": {"content": "search"}}}'

‍

List indexes

curl -k -u admin:<PASSWORD> https://<IP_DE_LA_VM>:30920/_cat/indices?v

‍

💡 Tip: OpenSearch is compatible with the Elasticsearch API. Clients like opensearch-py (Python), @opensearch-project/opensearch (Node.js), and the official Java SDK work directly. You can also use Elasticsearch clients by pointing to your instance's URL.