Configure Custom Hostnames

Configuring your own domain for a ClusterNest cluster is extremely simple - add a CNAME pointing to our domain customers.c9t.io, then set the custom hostname on the cluster.

OpenSearch

ClusterNest Managed OpenSearch Service exposes two independent hostnames - one for the OpenSearch API, one for OpenSearch Dashboards - each customizable on its own:

opensearch.example.com CNAME customers.c9t.io
opensearch-dashboards.example.com CNAME customers.c9t.io

Once the CNAMEs have been added, set custom_hostname and/or dashboards_custom_hostname:

Console

1. Open the cluster form: Launch Cluster for a new cluster, or Edit on an existing one.
2. Enter the OpenSearch hostname in OpenSearch Custom Hostname, the Dashboards hostname in OpenSearch Dashboards Custom Hostname, or both.
3. Save the cluster.

Terraform

resource "clusternest_opensearch" "logs" {
  # ...
  custom_hostname            = "opensearch.example.com"
  dashboards_custom_hostname = "opensearch-dashboards.example.com"
}

See the resource reference for every field.

Raw API

PUT replaces the whole cluster, not just the fields you send

Any field left out of the request body resets to its schema default, not its current value - GET the cluster first, merge in the change, then PUT the merged result back.

Secrets are the exception: GET never returns client_secret or secret_access_key, only client_secret_set and secret_access_key_set. Leave a secret out of the body to keep the stored one, or include it to replace it. The *_set flags are ignored on write, so the merged result can be sent back as is.

curl "https://api.clusternest.com/cluster/opensearch/$CLUSTER_ID" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  | jq '.custom_hostname = "opensearch.example.com"
      | .dashboards_custom_hostname = "opensearch-dashboards.example.com"' \
  > cluster.json

curl -X PUT "https://api.clusternest.com/cluster/opensearch/$CLUSTER_ID" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  --data-binary @cluster.json

Prometheus

ClusterNest Managed Prometheus has a single hostname to customize:

metrics.example.com CNAME customers.c9t.io

Set custom_hostname:

Console

1. Open the cluster form: Launch Cluster for a new cluster, or Edit on an existing one.
2. Enter the hostname in Custom Hostname.
3. Save the cluster.

Terraform

resource "clusternest_prometheus" "metrics" {
  # ...
  custom_hostname = "metrics.example.com"
}

See the resource reference for every field.

Raw API

PUT replaces the whole cluster, not just the fields you send

Any field left out of the request body resets to its schema default, not its current value - GET the cluster first, merge in the change, then PUT the merged result back.

curl "https://api.clusternest.com/cluster/prometheus/$CLUSTER_ID" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  | jq '.custom_hostname = "metrics.example.com"' \
  > cluster.json

curl -X PUT "https://api.clusternest.com/cluster/prometheus/$CLUSTER_ID" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  --data-binary @cluster.json

Either way, the CNAME has to resolve before the cluster picks it up - DNS propagation, not anything on ClusterNest’s side, is what most delays take.