Elasticsearch cloud offerings¶

Elastic Cloud is available through each major cloud provider's marketplace. Use the links below to review pricing and access each provider's offering.

AWS¶

• Elasticsearch Cloud Offering Pricing Calculator
• AWS Official Elasticsearch Offering

FIPS compliance requires a platinum subscription if using a cloud provider. See FIPS Compliance via FedRAMP Gov Cloud.

Azure¶

• Elasticsearch Cloud Offering Pricing Calculator
• Azure Elasticsearch Offering

GCP¶

• Elasticsearch Cloud Offering Pricing Calculator
• GCP Elasticsearch Offering

Datavolt¶

Elasticsearch¶

Datavolt services for LLM monitoring can be configured to use an external Elasticsearch over one provided by PCS. To accomplish this an Elasticsearch URL and credentials must be provided to Datavolt via values.yaml and k8s secrets object.

Datavolt version 11.9.58+¶

Connection URL¶

By default DATAVOLT_ELASTIC_SEARCH_URL / DATAVOLT_ELASTIC_SEARCH_LB_URL are built as {scheme}://{dr-common.elasticsearch.host}:{dr-common.elasticsearch.port}. component.app.elasticsearch controls this:

scheme: Toggle http/https for the constructed URL (default: https). Use this alone if the user's cluster is reachable at the same host/port dr-common already resolves, just without TLS.

urlOverride / lbUrlOverride: If set, used verbatim for DATAVOLT_ELASTIC_SEARCH_URL / _LB_URL respectively, bypassing the scheme/host/port construction entirely. Use this when the external cluster doesn't fit that shape (a different host, a non-standard port, a comma-separated node list, etc).

DATAVOLT_ELASTIC_SEARCH_URL is read by the main app container (ElasticSearchConfiguration.elastic_search_url in datavolt/config.py, a MultiHostUrl — it can be a comma-separated list of individual nodes).

DATAVOLT_ELASTIC_SEARCH_LB_URL is read by the migrate init container only (migrations/env.py), which needs a single reachable endpoint for esmigrate, not a node list. The main app container has no elastic_search_lb_url field, so this var is simply unused noise there.

By default, both are built from the same dr-common.elasticsearch.host/.port, so they render identically for the bundled Elasticsearch subchart. But urlOverride and lbUrlOverride are separate knobs so you can point the app and the migrate job at different addresses if the user's external topology needs it — e.g. a node list for the app to sniff across, and a single load-balanced endpoint for migrations.

component:
  app:
    elasticsearch:
      urlOverride: "https://es.user-corp.internal:9243"
      lbUrlOverride: "https://es.customer-corp.internal:9243"

Credentials¶

envs is a map keyed by env var name, so a single entry can be overridden without restating the whole map of defaults from values.yaml.

envs:
  DATAVOLT_ELASTIC_SEARCH_USERNAME:
    value: elastic # or whatever username the cluster expects
  DATAVOLT_ELASTIC_SEARCH_PASSWORD:
    valueFrom:
      secretKeyRef:
        name: customer-es-credentials # a Secret that must already exist in the namespace
        key: password

By default, DATAVOLT_ELASTIC_SEARCH_PASSWORD reads from the pcs-elasticsearch Secret (the one created by the bundled Elasticsearch subchart). If the user's cluster isn't managed by this chart, that Secret won't exist — override valueFrom.secretKeyRef above to point at wherever the user's credentials actually live.

envs:
  DATAVOLT_ELASTIC_SEARCH_USERNAME:
    value: null # required: values.yaml's default sets `value`, this clears it
    valueFrom:
    secretKeyRef:
      name: customer-es-credentials
      key: username
 ```

##### Put it together {: #put-it-together }

```yaml
component:
  app:
    elasticsearch:
      urlOverride: "https://es.customer-corp.internal:9243"
      lbUrlOverride: "https://es.customer-corp.internal:9243"

envs:
  DATAVOLT_ELASTIC_SEARCH_USERNAME:
    value: elastic
  DATAVOLT_ELASTIC_SEARCH_PASSWORD:
    valueFrom:
      secretKeyRef:
        name: customer-es-credentials
        key: password

The same scheme / urlOverride pattern also exists on component.app.auth for DATAVOLT_DR_AUTH_URL, in case the DataRobot Auth endpoint needs to be pointed elsewhere too.

Datavolt versions 11.2.x to 11.9.57 (deprecated)¶

values.yaml changes:

DATAVOLT_ELASTIC_SEARCH_URL: <elasticsearch URL>
DATAVOLT_ELASTIC_SEARCH_USERNAME: <elasticsearch username>

And the secret pcs-elasticsearch must be created or updated to contain the Elasticsearch password:

data:
  elasticsearch-password: <base64 encoded>

Datavolt version Release/11.1 (deprecated)¶

Contact DataRobot support for guidance on configuring external Elasticsearch for this release line.